These are chat archives for BSData/wh40k

22nd
Aug 2016
Universalerror
@Universalerror
Aug 22 2016 00:27
Should duplicate issues be closed immediately?
Earl Bishop
@DrTobogganMD
Aug 22 2016 02:17
I mean we won't kick you if you don't ...
But no need to leave dupes open if you see them
Amadeusz Sadowski
@amis92
Aug 22 2016 07:15
Guys, we have a few new and very eager contributors (see BSData/wh40k@7d616d8 & BSData/wh40k@ef9ce30). Could you please help them? Can anyone confirm if the already existing Deathwatch file (Deathwatch - Codex.cat) is deprecated or what? Guys are uploading new files, and the one already here has internal name containing (2016) which to me, without closer inspection, means it's already for the newest codex (was there even any for Deathwatch before?)
Troy Graber
@tag8833
Aug 22 2016 14:24
@amis92 No, there hasn't been an Older Deathwatch codex, but the Deathwatch codex came out in 2 parts with the 1st part being essentially 1 formation. That could be the file that currently exists.
Do we know who wrote that file?
I checked the file. The version that I have is indeed only the formation that came out in the Deathwatch: Overkill box, so it would be easier for someone to add / import those formations to a more complete version of the deathwatch overkill file than recreate all of the new units and formations in this file most likely. Let's just try to keep it the same name so we don't have people confused that there are 2 of them.
Amadeusz Sadowski
@amis92
Aug 22 2016 18:50
That (keeping the same name) will confuse people. Anything but updating the existing catalogue will wreak havoc in Issues and amongst community. If someone wishes, he can copy over manually (in some text editor) appropriate entries into existing catalogue, but the catalogue we have in repo must stay under the same name and with the same catalogue ID.
KwaiLoCDN
@KwaiLoCDN
Aug 22 2016 21:17
The file I uploaded does contain the Deathwatch Overkill information. Whoever made the 1st file named it well for when it was made, as at the time there was no indication of a further, actual codex. I have not done anything like this in the past, so feel free to edit, rename, etc etc the file I uploaded. I just wanted to be able to make a Deathwatch army on BattleScribe, and now can. If I can help further, I will.
Amadeusz Sadowski
@amis92
Aug 22 2016 21:18
Help is very much wanted, yes :)
However, if you already take time to contribute, please do so with our guidelines in mind. As already linked in some places, Developer Guide is most helpful, but Catalogue Naming Convention and other articles in that wiki are there for you too.
As I'm typing, I'm replacing the old file with yours but with old file's name and catalogue ID
Earl Bishop
@DrTobogganMD
Aug 22 2016 21:26
@amis92 could you do me a favor and copy it to bs2 as well. I'll load it up sometime this week to make sure nothing wonky happens
It shouldn't ... But best to be prepared. Necrons needed fixing when it was loaded up.
Amadeusz Sadowski
@amis92
Aug 22 2016 21:27
Oooh I'd rather not do that. I've not touched BS2 in anyway ever yet, so maybe someone else please?
Earl Bishop
@DrTobogganMD
Aug 22 2016 21:27
I just meant the repo lol
Pretty much me and Cartagena are handling the prep at this point
.... Can we just rename him @cartagena
My phone would be happier
Amadeusz Sadowski
@amis92
Aug 22 2016 21:28
haha I think you've actually mentioned someone with that handle xD
so you mean like, copy over the file as-is into bs2-prep repo?
Earl Bishop
@DrTobogganMD
Aug 22 2016 21:29
Huh. Well then.
Hi @cartagena
Yep just that
Saves me the copy over and like 5m. But since you're there :)
Amadeusz Sadowski
@amis92
Aug 22 2016 21:33
Yeah well I could but... Not sure if it wouldn't be better to release now, wait for bug reports and then after fixes copy it over.
KwaiLoCDN
@KwaiLoCDN
Aug 22 2016 21:36
I'd like to build the BS2 file from scratch actually. This one is ugly. Too many modifiers, and re-doing of units to get things to validate.
Amadeusz Sadowski
@amis92
Aug 22 2016 21:38
Yeah... honestly, BS2 is way too ahead to put much effort there for now. We should primarily maintain current repo. Jon will let us know month or so in advance when BS2 is ready.
Earl Bishop
@DrTobogganMD
Aug 22 2016 21:56
Fair enough.
@KwaiLoCDN - once you get bug reports/corrections, feel free to download the bs2 alpha and start building.
BattleScribe/Desktop-Alphas#1
cartag
@cartag
Aug 22 2016 22:27
For the last time, I am not a port city in Columbia! :)
BS2 has a LOT of nice features under the hood for it. If you've gotten sufficient work done on the file you built from scratch, why not just add the extra stuff to it after converting to BS2? Just make the ID the same, delete the other file, and go from there
KwaiLoCDN
@KwaiLoCDN
Aug 22 2016 23:54
To get validation for DW, I had to duplicate a lot of unit info, that I would have preferred to link to. Links wouldn't min/max count for me though. If there is ever an errata, that first file is done for. I want to make sure 2.0 can last until the next codex.
Earl Bishop
@DrTobogganMD
Aug 22 2016 23:55
Min/max works fine in 2.0 :)
cartag
@cartag
Aug 22 2016 23:57
Looking at v6 of the file, there is a LOT of redundancy here