BSData / wh40k-7th-edition

Warhammer 40,000: 7th Edition
http://battlescribedata.appspot.com/#/repo/wh40k-7th-edition
172 stars 271 forks source link

Move Fortifications INTO CAD etc #181

Closed amis92 closed 9 years ago

amis92 commented 10 years ago

So it struck me lately that we may enhance the error-proofness of our game system by including Formation Fortification category into the Combined-Arms Detachment.

It would mean that you cannot take a Formation Fortification Detachment, instead you take Formation Fortification directly in CAD. However, because we currently have a single catalogue with fortifications, it would have to be done as a nested force type inside CAD.

Or we just wait until there is that new awesome version of BattleScribe enabling us to move these into gst. (See https://github.com/BSData/bsdata/issues/39)

Well, after a second thought, maybe we better wait.

Kangodo commented 10 years ago

My vote goes to waiting too!

coruptcopy commented 10 years ago

Sounds brilliant, but if it'll be easier later, then perhaps it is best to wait. Maybe when we do this, we can combine all the factions too (except Imperial) so there will just be, for instance, 1 Chaos Space Marines faction that has all the vanilla, Black Legion, and Crimson Laughter in it. On Aug 4, 2014 6:32 PM, "Tim Sijben" notifications@github.com wrote:

My vote goes to waiting too!

— Reply to this email directly or view it on GitHub https://github.com/BSData/wh40k/issues/181#issuecomment-51131933.

ghost commented 10 years ago

As things stand, you could copy the Formation section into the CAD, but not move it, since a formation can be taken on its own as an ally.

What are the mechanics of nested force types? I'm thinking of when the Orks select the Great Waaagh detachment & get a different set of relics.

amis92 commented 10 years ago

@khambatta where/how else can it be taken? Looking through 7th edition I see Fortifications included only in CAD. Additionally if I remember correctly it can be taken in Ork detachment. But as an ally?

S for nested mechanics: Each force type, including nested, can choose different catalogue filter for starters. Further on, each force type must include at least one category.

I could tell more, but I don't understand how it could be used for relics for Orks?

Kangodo commented 10 years ago

Khambatta speaks of Formations, not Fortifications. So far each non-Allied Detachment can also take a Fortification. (CAD, Great Waaagh! and Ork Horde)

amis92 commented 10 years ago

Ah. I see.

But Formation Detachment as per logic contained in 7th ed is a detachment on the same level as CAD etc.

My goal here would be to be with force types as close to detachments as possible. That would mean we'd be nearly perfect in terms of allowing only legal combinations. One thing we cannot assert right now, and probably never will be, is taking Allied Detachment only with Faction other than the one with Primary.

axisofentropy commented 10 years ago

Don't nest any other detachments within Combined Arms Detachments. They're all first-class detachments. If the user experience issue is caused by poor documentation or poor interface, fix that instead.

Kangodo commented 10 years ago

I've been thinking some more about this lately. Especially now that we have the Assassins and the Imperial Knights. Users want to quickly 'take' that extra Detachment and I think the current way of adding them is quite sluggish. The weirdest part is that, for an Assassin, I have to go through all possible Detachments even though they can only use one of those. Same goes for Imperial Knights. Wouldn't there be an easier way to handle these things? Or things like the Inquisition and the Legion of the Damned, it's not like they can use any other Detachment.

If things continue this way with GW, we will be flooded with Detachments and that could make things complicated and bloated.

amis92 commented 10 years ago

@Kangodo I think that's more to be aimed at @Jonskichov than us devs (cat authors).

I fully agree. We absolutely need a way to stop this bloated flood of Detachments/Force Types for a user experience. And on the account of doing these importing thing, which will bloat number of catalogue files; some kind of control over what is displayed in a Add Force windows is essential.

Viper666-Qc commented 10 years ago

Just realised I posted something similar for this topic


It's getting pretty crowded in the Force Type as we find every possible detachments from every codice/dataslates/supplements.

Is their any way it could be improved?

I see the Parent Force section is always limited to "Roster". Could we use this for different 40k game system like Standard game, Apocalypse, Zone Mortalis, Planetstrike, Kill team and Spearhead. Using this section could allow to reduce the number of detachments available in the Force Type section.

ex:

Parent Force: Zone Mortalis Force Type available: Attacker, defender, combattant

Parent Force: Planetstrike Force Type : attacker, defender

Parent force : Standard Game Force type: any standard game detachment available (excluding those mentioned above)

Also, could it be possible to choose the Catalogue "before" choosing the Force Type in a way that it would limit the number of detachment available?

ex: Catalogue: Space Wolves codex Force Type available: CAD, Space wolves detachment, Company of the Great Wolf, Wolves Unleached, Allied detachment

Catalogue Imperial Knight Force Type: Imperial Knight Detachment

This last thing would be great because right now, for example, you can select a Inquisitorial Detachment with the Chaos Space Marine codex and once you fill an HQ slot with a CSM HQ, the detachment is valid.....


amis92 commented 10 years ago

@Viper666 see the link in OP.

amis92 commented 9 years ago

Half a year later and we have more force types than catalogues (or close to that ;) ). If any one has any new ideas, please share... We're in a dire need of improvement.

amis92 commented 9 years ago

Okay, seeing absolutely no chance of it being in any way changed, I'm closing it here.