These are chat archives for BSData/wh40k

6th
Jan 2019
WindstormSCR
@WindstormSCR
Jan 06 00:00
@sk_Father_Price_twitter the logic monster that makes it function:
Price Van-Saint
@sk_Father_Price_twitter
Jan 06 00:02
all that from the depths of your own twisted mind .. it's like looking through a grubby window into your psyche ... weirdo
Earl Bishop
@DrTobogganMD
Jan 06 00:10
having to manually remove an entry for every detachment is a pretty big deal
That's ... Ugly
If we can not have to do that I love the rest. It looks like it works well
WindstormSCR
@WindstormSCR
Jan 06 00:14
I could remove the auto-add and just leave it with a "min 1 in roster"
would require users to add it to one of thier detachments
Earl Bishop
@DrTobogganMD
Jan 06 00:15
I'm curious why it auto add for all of them
When things like chapter tactics don't
WindstormSCR
@WindstormSCR
Jan 06 00:15
it only auto-adds on creation of the roster
not all the time
so same way CT, etc work
Earl Bishop
@DrTobogganMD
Jan 06 00:16
Ah gotcha
WindstormSCR
@WindstormSCR
Jan 06 00:16
there we go
now that's just got a min/max 1 in roster setup
for knights you could just make an SSE called Knight Lance that adjusts the CP values (adds 3, 0 or removes 3)
or whatever the rule name is that gives them disgusting amounts of CP :P
Price Van-Saint
@sk_Father_Price_twitter
Jan 06 00:30
is it possible to make the auto add = 0 and then add +3 after some validation once the roster is done ? ... maybe look for warlords detachment and only add a onetime thing ?
WindstormSCR
@WindstormSCR
Jan 06 00:30
I removed the auto-add
Price Van-Saint
@sk_Father_Price_twitter
Jan 06 00:31
oh ok ... lol .. I'm taking my tired ass to bednow ... nighters
WindstormSCR
@WindstormSCR
Jan 06 13:11
I'm holding off on doing any other cats but SM until more discussion is had about the CP stuff (if needed)
Earl Bishop
@DrTobogganMD
Jan 06 19:30
Agdq has started if anyone likes to watch speed run games
tekton
@tekton
Jan 06 19:31
CharityHammer is still running on canhammer and bifpod
Amadeusz Sadowski
@amis92
Jan 06 19:32
@/all any input for BSData/catalogue-development#15 ? (catalogues localization)
Earl Bishop
@DrTobogganMD
Jan 06 19:34
Yep. Bad idea
Unless we have a dedicated maintainer for every language being localized
Localized files as part of the normal repo is not a good idea either IMO. You're duplicating the entire repo for every language. That will quickly get very large on mobile downloads
Amadeusz Sadowski
@amis92
Jan 06 19:49
Nooo, the translations would be in separate files.
both in repo and for download.
No reason I should have to download Spanish version to build English rosters.
Earl Bishop
@DrTobogganMD
Jan 06 19:56
But they would be part of the current repo?
Or a whole new repo
Amadeusz Sadowski
@amis92
Jan 06 20:02
I'd say a part of the current, but both options are on the table. :)
WindstormSCR
@WindstormSCR
Jan 06 20:03
I'd go with separate repo
also it would have to have a dedicated maintainer or two
Amadeusz Sadowski
@amis92
Jan 06 20:04
So, the catalogues would stay as they are, but we'd have, supposedly, an additional folder called l10n (localization) which would contain files that have just translatable words with some id's, and file per language with the translations of those ids.
The problem with separate repo is that logically dependent (and identically versioned) content would live in unassociated locations; also the number of repositories will boom out
WindstormSCR
@WindstormSCR
Jan 06 20:05
as long as it doesn't affect mobile size and is somewhat sane, I don't mind it
my other big worry is it somehow causing issues with the primary files
so something overwriting work that shouldn't
Earl Bishop
@DrTobogganMD
Jan 06 20:06
Is battlescribe able to read those amis?
Amadeusz Sadowski
@amis92
Jan 06 20:06
Has anyone actually read the issue? ;D
WindstormSCR
@WindstormSCR
Jan 06 20:07
I did, and understood some of it
Earl Bishop
@DrTobogganMD
Jan 06 20:07
Yes but I don't understand
WindstormSCR
@WindstormSCR
Jan 06 20:07
my opinion is the only clean way to do it is basically create something like USSX had for ynnari, that basically strips/reformulates the XML
Earl Bishop
@DrTobogganMD
Jan 06 20:07
If bs doesn't support localization how will it read these langauge tags
WindstormSCR
@WindstormSCR
Jan 06 20:08
I'm assuming some sort of appspot thing would
Earl Bishop
@DrTobogganMD
Jan 06 20:08
Unless the maintainers are supposed to add these for every language that comes up
WindstormSCR
@WindstormSCR
Jan 06 20:08
its pretty much a nasty rabbit hole from any angle
without built-in support
even with built-in support it would be a rabbit hole
Amadeusz Sadowski
@amis92
Jan 06 20:09
Yeah so you know that AppVeyor thing going on?
WindstormSCR
@WindstormSCR
Jan 06 20:09
I'm assuming you were going to do something with automation
Amadeusz Sadowski
@amis92
Jan 06 20:09
There's these build operations, artifact packaging and attaching .bsr to every release
Yes
So that process would be extended to support localization, probably.
The result would be that instead of a single .bsr, the process would produce a "primary" BSR file and additional one for every localization/translation.
WindstormSCR
@WindstormSCR
Jan 06 20:10
which is cool, but there is still the issue of the fact whichever poor fucker (excuse the phrase, but it fits) decides to localize, is going to have to put in the exact text for everything
that's not a one-man job
(I should know, I tried)
Amadeusz Sadowski
@amis92
Jan 06 20:11
True, but that person wouldn't have to do that at once. We could always default to the "primary" text in case no translation is found.
Of course that's not great, but translations never are. :D
amis92 @amis92 thinks "maybe except of Shrek's translation to Polish, which supposedly contained even better humor than original"
WindstormSCR
@WindstormSCR
Jan 06 20:16
so my position in the end is "don't care so long as there are safeguards against accidents"
and against it bloating mobile
Earl Bishop
@DrTobogganMD
Jan 06 20:18
Agreed. My concern is keeping things 1:1 and to not bloat mobile.
Otherwise im a simple Englishman
If others want to localize I'm all for support for it. But we should not be doing these localizations ourselves (unless one of us wants to I guess)
Simon Porter
@FarseerVeraenthis
Jan 06 21:16
my only question (since everyone else has thought about how it can be implemented from a software perspective) is where do we get the other language versions from, and where do we find new maintainers to just do the translations?!?!?!
Amadeusz Sadowski
@amis92
Jan 06 21:22
Well, obviously, if there are no maintainers to do a language, the language won't be done xD
So it'll rather be on a volunteering basis: "I want to do a translation to Xyz language" and then we get it
I don't see value in automatic translations, especially for such highly specialized domain with very unique nomenclature.
I guess we could expect German, French, Spanish and that's about it.
Simon Porter
@FarseerVeraenthis
Jan 06 21:25
that should cover a significant proportion of the world
but that's still quite a lot of work
and I totally agree, it would have to be direct from the GW texts
Dirk Bachert
@Thairne
Jan 06 21:30
considering how we are stretched thin with maintainers as we are, the additional work required to set it up, cover all potential bugs and fallbacks to default to EN in any case, having to deal with probably too few maintainers and the corresponding bug reps caused by typos, errors in translation and new rules condundrums (just imagine an italian BCB or something )... Not too much a fan of multi lingual cats because of the hazzle caused. Principal idea? Awesome, but like windstorm said... that's one fething rabbit hole.
also, Astartes EP 3 is out:
https://www.youtube.com/watch?v=CMGRa4_UjE4
WindstormSCR
@WindstormSCR
Jan 06 21:45
since it got buried a bit
any commentary from anyone about the CP totaling currently on master?
changes/improvements/etc?
Amadeusz Sadowski
@amis92
Jan 06 21:47
Didn't try it but it sounds really nice, finally being done in a semi-proper manner :)
WindstormSCR
@WindstormSCR
Jan 06 21:47
my eureka moment was when I was fucking with vigilus relics and ancestor conditions
and realized that was the one way to key off categories
Dirk Bachert
@Thairne
Jan 06 21:47
oh yeah
I like it. Implementation is a bit... stringy, but no other way to do it that I could think of.
I'm fine with it, adds something useful and reduces confusion