Sir R. M8gic1an
2009-09-09 12:44:41
Ok, so here is another piece of my plans.
Any thoughts on this?
MSI SVN will use [prefixes] on the threads for easy organization. This is how i'm thinking of it:
so we can easily see and keep it organized. Prefixes are great because you can actually use the search function for a single prefix.
For people to contribute and for everything to stay organized and run well this is what I had in mind:
PMs decide on which city and which skills
SLs then make a list of functions that would be needed to make a script for this city and these skills.
SLs are specific to the point of deciding on function names and function parameters.
e.g.
Functions needed:
And then whoever wanted to contribute would take a look at the function name, description and params and make it.
Any Ideas or opinions or suggestions on any of this?
~RM
MSI
| - Script Leaders Board
| - Planning
| - Discussion
| - Commits
| - Project Managers Board
| - General
| - MSI SVN (use prefixes here -> Similar concept to PubSVN)
| - Archive
| - MSI Announcements
| - MSI Current Projects
| - MSI Competition
| - MSI Scripts/Funcs
| - MSI Suggestions
Any thoughts on this?
MSI SVN will use [prefixes] on the threads for easy organization. This is how i'm thinking of it:
[core]
[Skill1]
[Skill2]
[Skill3]
so we can easily see and keep it organized. Prefixes are great because you can actually use the search function for a single prefix.
For people to contribute and for everything to stay organized and run well this is what I had in mind:
PMs decide on which city and which skills
SLs then make a list of functions that would be needed to make a script for this city and these skills.
SLs are specific to the point of deciding on function names and function parameters.
e.g.
Functions needed:
//function needs to find tree 'which' using the TTree type and returning the tree position to (x, y).
//Returns true if tree 'which' found.
Function FindTree(which: TTree; var x, y:integer):boolean;
//function needs to find rock 'which' using the TRock type and returning the rock position to (x, y).
//Returns true if tree 'which' found.
Function FindRock(which: TRock; var x, y:integer):boolean;
//needs to detect which is the best pick the player can wield,
//and then find the best pick available which the player can wield in bank.
//Returns which pick it is in the form of a TObj type to 'which' and returns true if pick withdrawn
Function WithDrawBestPick(var which: TObj): boolean;
//same as for WithDrawBestPick but for woodcutting axes
Function WithDrawBestAxe(var which: TObj): boolean;
And then whoever wanted to contribute would take a look at the function name, description and params and make it.
Any Ideas or opinions or suggestions on any of this?
~RM