On Mon, Jan 4, 2010 at 10:10 AM, Guangcong Luo <[email protected]> wrote: > As the branches diverge, they won't be so easily backported. > > And having to have two games that are effectively the same thing, but > one for campaign and one for skirmish, as they diverge... It'd just be > a nightmare for users as well as devs. I don't think it would reduce > anyone's workload.
But that is already true. Campaign and skirmish is rapidly diverging. The game rules are increasingly and markedly different, and the code has an increasing, not a decreasing, number of exceptions for campaigns. I used to think that we ought to synchronize the rulesets between skirmish and campaign, but now I think that is neither feasible nor desirable. Not feasible because it is too much work and chance of bugs and imbalances, and not desirable because it would change the original campaign a lot and it really ought to stay the way it was. >> That is what we keep thinking, and yet about every release we get new >> campaign bugs. Those are always the bugs that are found last and fixed >> even later. > > I think the solution is for all devs to just skim through > transporter.c, mission.c, and message.c. That is not a solution. Besides, some of that code is really incomprehensible. > Our main problem is that we assume units are always on the map. But in > a campaign mission, they're often not on the same map as the currently > active one. Maybe we should have some more abstraction. But we are not moving toward more abstraction of this code. We are moving toward ever more exceptions. Case in point: > See: http://developer.wz2100.net/changeset/8965 Campaign always being a low priority item on everyone's agenda, throwing a near total rewrite of that code up in the air as an idea gives us very little. In fact, it would be much easier to rewrite it if we can remove the burden of having to maintain the original campaign while doing it. - Per _______________________________________________ Warzone-dev mailing list [email protected] https://mail.gna.org/listinfo/warzone-dev
