New repo: X-wing 2.0 about catalogue-development HOT 10 CLOSED

Please discuss it with the x-wing repo maintainer in an issue opened in that repository. We do not practice "new repo for new edition" with very few exceptions, like the 8th ed of 40k.

from catalogue-development.

That's the repo: https://github.com/BSData/swxwing

from catalogue-development.

Just a question, but what would qualify a repo for an exception? I've opened a ticket on the x-wing repo, but feel like there won't be any plans to update due to major format change the new edition has.

from catalogue-development.

To answer shortly, there are no specific indicators or conditions for an exception. That one time it was done for 8th was a long discussion, and it was a result of many, many changes we were doing, including reorganization of the team structure, the organization structure, repo access rights, complete rewrite, a very strict and announced cutoff of the 8th (index thing, all new rules), and so on. There are others, like Firestorm V2 I believe, but that's a legacy issue never consulted with me, and Necromunda, which is another misunderstanding and also a little bit of naming chaos GW introduced with Gang War and Underhive.

Paging BSData/swxwing#23 for reference

from catalogue-development.

So here's the deal, I'm ready to upload an X-Wing Second Edition catalogue but it is a 100 percent re-write. I started from scratch and didn't reuse anything from the old catalogue. Second Edition has some major rules reworks, a different point structure, and different factions. It's not like 40K where a codex might be compatible into the next edition - all unit information was completely reset from the ground up for this new edition of X-Wing. I've come around to thinking that this should be a new catalogue, rather than an incremental update of the old X-Wing catalogue. Plus, given that there are still people out there playing X-Wing first edition, if I update that catalogue and they update their data, it will nuke all their squad lists.

Is it possible to just archive the 1.0 repo and open a new one called "Star Wars: X-Wing (Second Edition)"?

from catalogue-development.

I'm reluctant to creating new repository. For all the reasons I've mentioned previously (and others), 8th ed for 40k was an exception. Which won't happen again.

If you've created a new game system from scratch (so that the game system ID is different), there will not be any problem with the people that already have the old datafiles. They'll just download new files besides the old ones. The old files won't be easily available (through AppSpot/BattleScribe interface), but that's not really an issue, is it? For those that care, you can provide a link as we did in 40k.

It'd be a good idea to have the 2nd ed. in the game system name, so it's visible immediately and doesn't clash internally in BattleScribe with old rosters.

from catalogue-development.

Oh yeah, that makes sense. I'll do that tonight. That works.

However, while we are on the subject, can a repo name be edited? It's always bugged me that the name for the X-Wing repository lacks a colon (Star Wars X-Wing), so it isn't formatted the same as Fantasy Flight's other Star Wars games (Star Wars: Armada and Star Wars: Legion). If it is possible to edit the name of the X-Wing repo to add the colon (without changing the url or anything)? If not, no big deal.

from catalogue-development.

Yeah, you can edit it, no breaking changes there. There's an "edit" button nearby.

While you're changing up things, could you fix up README formatting? You can use the updated template or just fix manually.

from catalogue-development.

Alright. The catalogues are happy and I updated the README formatting. However, I'm still not sure where to change the actual name of the repo (as it displays on the battlescribedata.appspot.com page). That's where I want to add the ":" into the repo title so it matches the formatting of the other FFG Star Wars games.

from catalogue-development.

on the repo's main GitHub page, on the far right to the repo title, you should have "Edit" button.

from catalogue-development.