Gentlemen,
As the source code project seems to enter some kind of "almost final stage", a huge amount of work remains to adapt all the existing mods and of course I am still hoping for new mods and perhaps even new modders to come.
Since I completely lost track of all the new features (functions, variables, textfile modifications ...) introduced by the source code project (despite an early attempt to achieve some documentation
), and I assume the only people who know what's in the source and what needs to/can be done in a Mod are the members of the Source Code Project who worked on particular functions, I thought a wiki would possibly be the most feasible way to collect the information.
Voilá -- here it is.
It's very simple, hopefully easy to use, and currently it's totally open -- anyone may create and edit pages (let's face it: we are a minor community no serious spammer would be interested in
).
I created some initial pages with information about functions and variables I already knew about -- these pages serve as examples and of course they may be edited for more detailed information
. You will also find an easy way to add pages in the sidebar -- just type in the desired pagename after the prefilled groupname: If the page already exists it will be displayed, otherwise you will be prompted to create a new page.
There are four groups for "Database" (textfiles), "Functions", "Events" and "Variables". More general information like e.g. about the (fixed?) scenario structure could go into "Main" (which means creating a page like "Main.Scenarios"). Another page could be "Main.NumberOfSprites" to let the world know about the number of sprites possible in the modified program.
It's not a secret: You may easily create a new group, too
. Of course this should be considered carefully.
There is one restriction concerning SLIC variable names and wiki page names: Since the wiki itself uses dots to separate groupnames from pagenames we cannot use dots in pagenames for SLIC variables -- we need to "convert" them to WikiWords (e.g. player.government -> PlayerGovernment) and give the real variable name in the text. No, this cannot be worked around within the wiki system, but I think we can live with it.
If you experience any oddities or malfunctions or if you wish to make any suggestions please don't hesitate to post to this thread
.
Please, gentlemen, comrades, estimated members of the Source Code Team: contribute!
As the source code project seems to enter some kind of "almost final stage", a huge amount of work remains to adapt all the existing mods and of course I am still hoping for new mods and perhaps even new modders to come.
Since I completely lost track of all the new features (functions, variables, textfile modifications ...) introduced by the source code project (despite an early attempt to achieve some documentation

Voilá -- here it is.
It's very simple, hopefully easy to use, and currently it's totally open -- anyone may create and edit pages (let's face it: we are a minor community no serious spammer would be interested in

I created some initial pages with information about functions and variables I already knew about -- these pages serve as examples and of course they may be edited for more detailed information

There are four groups for "Database" (textfiles), "Functions", "Events" and "Variables". More general information like e.g. about the (fixed?) scenario structure could go into "Main" (which means creating a page like "Main.Scenarios"). Another page could be "Main.NumberOfSprites" to let the world know about the number of sprites possible in the modified program.
It's not a secret: You may easily create a new group, too

There is one restriction concerning SLIC variable names and wiki page names: Since the wiki itself uses dots to separate groupnames from pagenames we cannot use dots in pagenames for SLIC variables -- we need to "convert" them to WikiWords (e.g. player.government -> PlayerGovernment) and give the real variable name in the text. No, this cannot be worked around within the wiki system, but I think we can live with it.
If you experience any oddities or malfunctions or if you wish to make any suggestions please don't hesitate to post to this thread

Please, gentlemen, comrades, estimated members of the Source Code Team: contribute!
Comment