Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 14:40
    BSDataAnon opened #1115
  • 04:36
    BSDataAnon opened #1114
  • 00:53

    cartag on cartag

    Mawtribe Update Including Kin-… (compare)

  • 00:48

    cartag on cartag

    Nighthaunts updates Also Legio… (compare)

  • 00:48

    cartag on cartag

    Ogor fixes Banners, Hornblower… (compare)

  • 00:47
    cartag commented #1108
  • 00:47
    cartag closed #1108
  • 00:46
    cartag assigned #1108
  • 00:46
    cartag closed #1109
  • 00:46
    cartag commented #1109
  • 00:45
    cartag assigned #1109
  • 00:45
    cartag closed #1110
  • 00:45
    cartag commented #1110
  • 00:38
    cartag assigned #1110
  • 00:38
    cartag commented #1110
  • 00:32
    cartag closed #1112
  • 00:32
    cartag commented #1112
  • 00:32
    cartag assigned #1112
  • 00:32
    cartag closed #1113
  • 00:32
    cartag commented #1113
Iain Launchbury
@Mad-Spy
I might change all of mine :)
OftKilted
@OftKilted
:+1:
Iain Launchbury
@Mad-Spy
@/all, to make everyone's life easier when splitting, GA traits and Artefacts should be in the GST. Please move yours.
Iain Launchbury
@Mad-Spy
see #175
OftKilted
@OftKilted
.... and I was doing so good ...
Iain Launchbury
@Mad-Spy
Got to keep you on your toes :)
OftKilted
@OftKilted
Dang moving goal lines ... let’s line up for another try.
Next thing we’ll have “Battalion Validation” To input ...
OftKilted
@OftKilted
@Mad-Spy Did you actually submit your commit on the GA Traits and artifacts?
I'm not seeing it posted
Iain Launchbury
@Mad-Spy
I did it in my oe
OftKilted
@OftKilted
oe?
Iain Launchbury
@Mad-Spy
My Own branch didn't I?!
And forgot to merge it...
OftKilted
@OftKilted
takes out the poking stick and pokes @Mad-Spy
"Chaos is already done ...." looks at the get ... finds nothing ... Sneaky-sneaky chaos ....
OftKilted
@OftKilted
If you qualify for Allegiance X. And also the GA. You can choose to entirely use the GA Allegiance Traits. Does that mean that you're using Allegiance: <grand alliance> or that you're just using the traits? (See: Allegiance: Tomb Kings ... and Battleline for Tomb Queen ... No Allegiance Traits for TK)
Almost makes one want to set up an 'Allegiance: X (GA:<grand alliance>' allegiance
Iain Launchbury
@Mad-Spy
Just using the abilities.
OftKilted
@OftKilted
That makes more logical sense.
Lemme know when you're going to do the merge, so I can coordinate dropping the Death GA abilities into the gst.
Iain Launchbury
@Mad-Spy
Just merge yours whenever. Mine will go in via a PR.
OftKilted
@OftKilted
We may not test our code often ... but when we do ... we do it in Production.
tekton
@tekton
good news: figured out something I was doing wrong
bad news: that was a wasted night...
OftKilted
@OftKilted
@tekton I know the feeling. Managing Catalogues that have multiple Allegiances (other than just the GA and the default) is nearly headache inducing. I’m a hairbreadth away from just splitting them out (Soulblight, Nighthaunt ... I’m looking at you .... :angry: ) to make catalogue management easier with the Allies forces... hmm ... perhaps there is an easier method
OftKilted
@OftKilted
So ... if one does a “constraint” on the Allegiance, based on the Category entries one could flag ‘bad’ units when building a list.
It wouldn’t hide them, just make a list validity warning. :thought_balloon:
OftKilted
@OftKilted
That might entail more categories in the gst ... hmmm.
Not optimal. :/
OftKilted
@OftKilted
@Mad-Spy What if we were to do this a different way for the Limitations?
If instead of hiding or showing, what if one did modifiers on the Categories?
For example: Nighthaunt
Set a max in roster of -1 by default.
If allegiance 'Derathmages' set Max in Roster to 0
Deathmages
If the units are categorized properly, it should flag that the restriction isn't being met ...
OftKilted
@OftKilted
It just makes gst'izing the keywords not as helpful.
Or reverse it ...
OftKilted
@OftKilted
Set Max 0 selections in Roster (child selections/child forces). Modifier - a decrement MAX 0 Selections by 1 OR <list of allegiances>
While one could set the default for the show the actual 'validation' is more of a 'too many selections of <category> in Roster
The only issue that I'm seeing is that for shared categories you can't add local modifiers.
shared from the gst
Iain Launchbury
@Mad-Spy
I had looked at that before. If you can make it work, write it up. I couldn't get it to work without moving the Force Entries to the individual catalogues, which has its own problems.
OftKilted
@OftKilted
The issue I was having in testing was that if a category isn’t in local, constraints can’t be modified.
OftKilted
@OftKilted
It looks better for doing a nested case statement for managing multi setups
For situations where there are multiple possibilities for Allegiance in a given cat. “Easiest” is splitting out each of the Allegiances. But that ends up with catalogue overhead.
Simon Barlow
@FreylisUK
Any thoughts at the moment on what we do about scenery i.e. the Balewind Vortex and Sylvaneth Wyldwood? Should we put them in the GST?
OftKilted
@OftKilted
For the time being.... I wouldn’t worry about them seriously. They probably need to be in a Scenery Catalog
There is a bunch of it.
Simon Barlow
@FreylisUK
Is it worth at least putting those two in given they have points values? I like to run a Vortex with my Tzeentch and it's a pretty common addition to a force.