Warzone 2100 Forums

Well, there is always way like this:
http://www.sqlite.org/amalgamation.html
(for releases to be included in game only)

OK, so common parts for all "profiles"?
Then I wouldn't split them, separate changelog for each file is minor benefit, you could simply use prefixes in commits messages to mark these changing specific aspects.

I believe that in case of tarball you need to skip autogen.sh step:

NoQ, could you define those "AI aspects"? That would make things clear also for me.

aubergine , it's interesting concept with power consumption, but don't really fits into WZ where everything except creating units and structures is free. I agree that in that case they could require working power generators but other parts of the idea are a bit too complex for me (but would fit int...

NoQ , uhm, I have no idea what used to be there. ;-) Although personally I think that splitting code that will be always loaded doesn't make big sense, but if script will be deciding what to load (like deciding which personality profile to use) then it makes sense to put them into separate files (t...

NoQ, to be clear, you want to put each profile into separate file or use separate files for different profile aspects?

aubergine, whatever, if someone will volunteer (ideally at least two) then why not.
But I still find planet being more flexible and more automatic.
Also most of bigger projects decide to use such solutions instead of shared blogs, surely for a reason.

For those who don't already know, there is Qt based map editor in the works (since 2010) and it needs some new developers to help with it's progress. Current state: loads maps that use current format; renders loaded maps in 2D view (remember to set data path first); non functional 3D view (currently...

aubergine, that depends on users themselves. I only want to say that shared blog will be bigger burden than planet.

aubergine wrote: IMHO .ini and .js go hand in hand, with .js being mainly for dynamic stuff and .ini for static stuff. JS is fairly easy to read, .ini is very easy to read. etc. They have slightly different pros and cons, but they compliment each other very well IMHO.

I agree.

aubergine , output etc. can be always customized. ;-) But in case of "shared" approach we will need at least one moderator and those who want only to share their content from their existing blogs will need to have two copies of one content etc. Just example case (I'm not sure if there is ...

aubergine , I can't agree that quick glance will be always enough to comprehend layout of whole campaign, surely it is possible with current ones, linear. For more complex it would require (at least for many users) some kind of graphical diagram. :-) About second suggestion, it is always better to ...

aubergine , probably it would be best to go for planet directly and let users decide which platform they want to use, only requiring it to be compatible. There could be some kind of guidelines for them that would help to get account on blogspot etc. or setup own blog from scratch. One blog shared b...

The one of issues with Warzone is that there is nearly no PR (as Public Relations) work done, which would be especially useful now, when we are going to finally see long time awaited new major release. So I'm proposing some preparations like creating new content dedicated to new release (maybe some ...