It wasn't me taking pot shots, it as me giving reasoning behind why using unitsync is not the solution to the issue. I was explaining that unitsync isn't always present and adding it as a dependency could require adding spring itself as a dependency to build the entire lobby whereas tasclient and spring lobby don't need to bother with that as its assumed spring is already compiled and configured before the lobby is ran. I do not have that luxury.Masure wrote:In the other hand, by making your lobby "not Spring dedicated" YOU are making things harder. I think Spring is complex enough to avoid taking other game engines into account and forbid unitsync usage.
This is not the point here and shouldn't be considered to criticize tasclient SP mode. A lot of things have to be improved but not in this way.
TASClient Single Player mode, Missions and Campaigns WIP
Moderator: Moderators
Re: TASClient Single Player mode, Missions and Campaigns WIP
Re: TASClient Single Player mode, Missions and Campaigns WIP
Why the hate on AF? It would actually be harder if we were to make a competing format...
Re: TASClient Single Player mode, Missions and Campaigns WIP
if you guyz talk about the missions, it has been made with collaboration ... i talked to braindamage ... and i repeat BUT FOR THE FUCKIN LAST TIME, i made a first step to a campaign and mission system, but we can still improve it and change whole part of it ... but if you just fuckin whine and don't make suggestions just go away !!
if you talk about tasclient single player's mode, iirc SL's dev didn't ask me when they made they skirmish mode ... because it's SL's single player's mode so they don't have to ask anything to anyone ... so STOP talking about the TASClient SP which, even if it uses HTML and supports skins is TASClient and ONLY TASClient's SP mode ...
edit: no more argue about the ssk file, nor TASClient SP, please, you can make features request or post bugs about it but that's all, ssk = delphi file for tasclient nothing else. Let's talk about missions and campaigns please.
if you talk about tasclient single player's mode, iirc SL's dev didn't ask me when they made they skirmish mode ... because it's SL's single player's mode so they don't have to ask anything to anyone ... so STOP talking about the TASClient SP which, even if it uses HTML and supports skins is TASClient and ONLY TASClient's SP mode ...
edit: no more argue about the ssk file, nor TASClient SP, please, you can make features request or post bugs about it but that's all, ssk = delphi file for tasclient nothing else. Let's talk about missions and campaigns please.
Re: TASClient Single Player mode, Missions and Campaigns WIP
I disagree, GUI and campaigns are tightly linked. Especially if you want multiple branching missions.
And you didn't discuss this with me, or any of the other spring lobby developers, or any developers who have not made their projects public knowledge. There were also rumours of work on this issue by lurker, and random comments on possible intentions for licho. Argh also appeared to have ideas.
And you didn't discuss this with me, or any of the other spring lobby developers, or any developers who have not made their projects public knowledge. There were also rumours of work on this issue by lurker, and random comments on possible intentions for licho. Argh also appeared to have ideas.
Re: TASClient Single Player mode, Missions and Campaigns WIP
I'm sure both Satirik and the springlobby people can work together to make a nice single player solution.
And it is too bad BrainDamage is busy with RL atm since he and Satirik already talked about this some.

Re: TASClient Single Player mode, Missions and Campaigns WIP
i splited this thread into two threads, a TASClient SP mode ... and a Missions and Campaigns mode, where we can discuss my prototype and improve it
so please could a moderator lock or even delete that topic ?
so please could a moderator lock or even delete that topic ?