Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 11:55
    UrsinePatriarch commented #1140
  • 11:53
    UrsinePatriarch opened #1144
  • 10:28
    UrsinePatriarch commented #1042
  • Dec 13 18:47

    OftKilted on master

    Merge pull request #6 from BSDa… Fixed Nagash problem, more to f… Fixed Nagash, incremented prope… and 1 more (compare)

  • Dec 13 18:47
    OftKilted closed #1143
  • Dec 13 18:39
    UrsinePatriarch opened #1143
  • Dec 12 16:09
    cartag commented #1042
  • Dec 11 16:26
    Tigerwraith commented #1138
  • Dec 11 13:53
    alphalas commented #1042
  • Dec 11 13:51
    alphalas commented #1042
  • Dec 11 13:48
    Ginjitzu commented #1042
  • Dec 11 12:50
    alphalas commented #1042
  • Dec 11 12:50
    alphalas commented #1042
  • Dec 11 12:49
    alphalas commented #1042
  • Dec 11 07:40
    Ginjitzu commented #1042
  • Dec 11 04:34
    BSDataAnon opened #1142
  • Dec 11 00:29
    cartag commented #1141
  • Dec 11 00:27
    cartag commented #1141
  • Dec 10 22:10
    crownedzoidberg edited #1141
  • Dec 10 22:08
    crownedzoidberg opened #1141
WindstormSCR
@WindstormSCR
with AoS rules being free there is zero excuse for them to not have the proper ref anyway
Iain Launchbury
@Mad-Spy
The Battletomes with the Battalions in aren't free.
WindstormSCR
@WindstormSCR
I meant the units that get scrambled
Iain Launchbury
@Mad-Spy
Oh right. True.
WindstormSCR
@WindstormSCR
so two things about categories in SSEs
1) don't make them 'primary'
2) make sure the battalion constraints on SSEs are not shared
and it all works
Iain Launchbury
@Mad-Spy
We have primary categories in 40k and it works ok?
WindstormSCR
@WindstormSCR
I was getting odd double-count issues when I did primary in the aos sses
but as long as they have the right ones and none marked primary it works fine
Iain Launchbury
@Mad-Spy
Ok. I'll have a look later.
Iain Launchbury
@Mad-Spy
@WindstormSCR, your solution works. There just a small niggle in that units which switch battlefield role will show both categories.
WindstormSCR
@WindstormSCR
option 2 is just use the categories that will show in battalions, since root cats should override
OftKilted
@OftKilted
@Mad-Spy what stuff does the switch? (Drawing a blank)
Double counting battalions is also bad as the number of battalions determines the numbers of artifacts available
Iain Launchbury
@Mad-Spy
There are duplicate RSEs with different primary categories. Not sure what you mean about double counting?
OftKilted
@OftKilted
In the picture for the layout you can see “categories: Battalion, battalion”
If, at some point, we’re going to do validation for number of artefacts, double counting is not the hotness
Ie counting the battalions twice
Iain Launchbury
@Mad-Spy
I don't see the duplication in my version of the implementation, so it may just be something that @WindstormSCR did when he was building his version
or are you just talking about the naming convention? All the battalions in Chaos are prefixed "Battalion:" in their name.
we can remove that easily
I see now in the image. I don't get that in my version, so I think we'll be fine.
Iain Launchbury
@Mad-Spy
image.png
Iain Launchbury
@Mad-Spy
I love that that battalion can be 920 -8890 points.
OftKilted
@OftKilted
At the top you can see categories: Battalion, Battalion
That being said, I’m not as big a fan of “Unit(Wizard)”
Are we going to do “Unit(Priest)”?
And “Ability(Command)”
Abilities (Battalion)
Iain Launchbury
@Mad-Spy
I agree on Wizard. It should be a separate item like psyker in 40k. I quite like abilities being separated.
OftKilted
@OftKilted
The issue I have is that they’re “Battle Traits” and “Command Traits”
Battalion Abilities being flagged that these are Abilities from the Battalion isn’t a bad idea. I’m just more of a fan of calling them what they are.
And from an aggregate perspective, an ability is an ability.
OftKilted
@OftKilted
Though there are both command traits and command abilities. And they’re explicitly separated. Hmmmmm
I’ll defer to your judgment on the Abilities
Iain Launchbury
@Mad-Spy
Comand Traits
Command Traits come from Allegiance though right?
OftKilted
@OftKilted
Which are different
While “Command/Unit/Battalion” Abilities are still Abilities (as are spells and prayers)
Defining their source could be helpful in understanding where something comes from and what gets access
I think that’s a good call.
Still more in line with making Wizards/Priests/Totems like psykers in 40k
The objective is to make the tool help players, and easy to understand what the opponent has when you read their list. Separating out the Ability sources will facilitate that. And due to constraints on how the data is presented probably will help clarification
OftKilted
@OftKilted
Still would like us to seriously consider clearing the Unit(Wizard) unit type and get them potentially flagged as a Category, or managed the same way we have it done in 40K for psykers
I’d be behind that kind of move 100%
Iain Launchbury
@Mad-Spy
We should be able to remove all the characteristic except cast/unbind and powers and not lose current data. Then we'll just need to add unit stats for any wizards.
OftKilted
@OftKilted
Cast/Unbind is actually a function that isn’t wizard specific. Priests have it as do other units.
For wizards it’s under the “Magic” label.