These are chat archives for BSData/wh40k

14th
Nov 2017
Jon Kissinger
@alphalas
Nov 14 2017 02:35
#1752
I vote no
Joe Beddoe
@CrusherJoe
Nov 14 2017 02:36
I would actually love to see that
Jon Kissinger
@alphalas
Nov 14 2017 02:36
That’s just - I don’t even what to know how much validation we’d actually have to do to get it to work right, consistently
Want*
Jebus I’m tired
That conversation I had with DJ drained me
WindstormSCR
@WindstormSCR
Nov 14 2017 02:49
it'd be like power level increments I'm guessing, and be annoying as hell
the CP thing isn't bad since that's just a main GST thing that doesn't touch every single file
Earl Bishop
@DrTobogganMD
Nov 14 2017 04:38
The name thing is possible
It’s ugly as fuck and not worth it.
But possible
As for cp count don’t we list cp per detachment already?
WindstormSCR
@WindstormSCR
Nov 14 2017 04:39
yeah, it just can be difficult to correctly track that with the way soup detachments are output
that's really where I can see a decent use for it, in mixed comps
Earl Bishop
@DrTobogganMD
Nov 14 2017 04:40
That could be ... easier but still require user input
It’d be a case of a validation error thrown if less than required cp are taken
Set at gst level
The model count in name however I wouldn’t even entertain. That will look bad codewise for very little benefit.
Set command point as shared entry with no profile and min max 0. Set as no org. Set increment min max by x based on y detachment.
Doing it automatically is tricky if possible at all (I don’t beleive it is)
WindstormSCR
@WindstormSCR
Nov 14 2017 04:45
I think there is using parent-child relationships
I'll see if I can make it work with a fork of the mobile
basically only incrementing a CP value based on if parent ant not a child force
so it would only register the highest level detachments
Earl Bishop
@DrTobogganMD
Nov 14 2017 04:47
Possibly. If it can be automatic sure. I’m against more user input.
And just like that I vanish into the night. Ping me if you need a head to bash ideas against
WindstormSCR
@WindstormSCR
Nov 14 2017 07:08
nope
can't make it happen because there is no way to attach a cost value to the roster
pity, because if you could define CP as another cost type you could do interesting things with stratagems too, like select the ones you plan to use and how many times, and build lists to give you enough CP to meet that
but since a force or category link doesn't allow that, there is no way to automate the CP addition at all :(
not without a hideous workaround that is too obnoxious to consider