Amadeusz Sadowski

@AlexMorman I think it might take some time. Maybe we can parallelize work and you could start writing down some simple, generic scenarios based on an existing dataset you've used...

@rahtolsGitHub It's not the best place, let me show a better one: https://github.com/BSData/phalanx/discussions/11 (there are similar do/don't like lists in the [Ideas discussions](https://github.com/BSData/phalanx/discussions/categories/ideas) for both Roster and Data editor.


🤦

We still refrain from hosting fanmade datafiles (or fanmade extensions). However, we now have a nice guide on how to host your repositories more conveniently so that they're easily accessible...

@Guy-Markman @DarkSkyT9A these requests are not so much for data itself, rather for BattleScribe *app*. What this was meant for are features for our *online* operations, features, how this organization...

The issues that I see are as follows (ordered from most to least important): 1. Do we create new repository for every new localization of every other repository? My view...

For the record, there was a discussion on gitter (permalink to first message: https://gitter.im/BSData/wh40k?at=5c3257d13cf6c35a849f036f) Screencap (hidden for brevity): 

@afcj's solution requires BattleScribe to know about this. We don't have the ability to introduce that feature. The one-off solution is easy, of course. Keeping all of this under tabs,...

For you and for me, sure (I'm from Poland, we don't even get translations for most wargames). If you're up to writing up something like that, feel free. I don't...