Senor NoirSol wrote:QUOTE (Senor NoirSol @ Jul 29 2017, 05:43 PM)
https://github.com/FreeAllegiance/Allegiance <----- This is our ONLY OFFICIAL CODEBASE
@KJGV please backport your code and issue list into the above repo^
As stated already my code is a fork toward a single player game (but with a game server and later on multiplayer features).
I've already trashed and changed too many things to go back. I've dropped everything AGC, OLE/COM and registry related. In fact my plan is to have the server and the client to run on Linux too (and yeah that means getting ride of DirectPlay and Direct3D).
It's a mid term project not compatible with your short term plan to reboot Alleg on Steam. I might eventually end up on Steam too but it will be a completely different game (don't expect anything on that front before mid 2018).
I will keep my changes open for now, here:
https://github.com/kgersen/Allegiance/tree/kgwork (notice: it's in a special branch 'kgwork' so the master branch is still in sync with your FreeAllegiance/Allegiance).
You're free to "cherry pick" changes from this branch , I think it's the easiest way to proceed for the time been.
I need to take a more days if not weeks to think more in details about how we can eventually cooperate, I care about an Alleg reboot on Steam but I already see too many sudden excitements and hasty decisions here. May be our projects can merge back together later on, in a few months, but it's too early.
I don't work like this, there is no real rush here. The new licence/steam stuff doesn't miraculously solve old problems, it doesn't change much in fact, except that most people loudly voicing their opinion aren't 'doers' so they won't contribute anymore now than before...on the manpower front nothing has changed yet. May be start advertising for devs on Steam and whatnot.
I really think everyone need to clam down, take a deep breath or in a few weeks that whole excitement will be gone and we will be back to where we were (I hope not but I'm afraid we will).