Spring RTS Engine

Well I was just looking through the wiki and it seems its got alot of information thats the old fashioned way of doing things.

Would anybody object to me going through and kicking the guts out of it and replacing them with stronger, faster, better than ever before guts?

Is is about improving the wiki? Pls do.

Zenka wrote:Is is about improving the wiki?

Violently...

Sinbad already tries to do this stuff all the time. I barely even touch the wiki any more, it probably needs tonnes of help.

Go for it.

Yeah... feel free to unbreak the wiki... I poke at it every once in a while but it's not a one man job... and I'm REALLY lazy.

Most thanks.


bewarn, you may get kicked in return :)

To be deleted, please say why it should be spared or it will go...

-http://taspring.clan-sy.com/wiki/Mod_Development:Spawn
Reason - WTF we have AI's now

http://taspring.clan-sy.com/wiki/Units:Download_TDF
Reason - Outdated system, new one is better

There is nothing 'new' about the now in-vogue sidedata.tdf method. leave it in, for those who are editing older mods it will remain useful.

Information about systems that are still in use should be kept, The wiki is the last resort referance. We don't want to delete stuff about old TA scripting standards or 3do modeling because spring modders might still have to work with that stuff and the information has to be available somewhere. However, the introductory stuff can go, they are fine purely technical. New mod makers don't need to know the old stuff until they know the new stuff already.

Unless anyone has any objections, I'd be interested in cleaning up http://taspring.clan-sy.com/wiki/Strate ... _Resources so that the tone's a bit more polite. (IE, removing things like "Don't argue - just do it!") The advice seems good, but the tone may be offputting for newbies.

That's because the author is a trolling/flamer... feel free to make it more proffessional... wiki's are for facts.

SinbadEV wrote:That's because the author is a trolling/flamer... feel free to make it more proffessional... wiki's are for facts.

Okay. The advice seems good, though.

Optimally the wiki is informitive and non emotional. However, a little character isn't terrible.

SwiftSpear wrote:Optimally the wiki is informitive and non emotional. However, a little character isn't terrible.

Edit done. I think it now meets the "a little character" criteria. I added a few tips gleaned from other threads around the board, I'd appreciate it if someone could sanity-check it. I also cleaned up the grammar a little. The spelling might alternate between British and American conventions. I tend to do that by accident. If anyone's bothered enough by that to feel like correcting it, go ahead.

As a canadian, as long as colour is spelled correctly I don't get pissed off... even though when coding you have to spell it wrong... grrr... stupid americans inventing the computer and all the most popular programming languages...

Not precisly on topic (but close enough I hope):
I´ve proposed an idea on the discussion of the Main Page, and I´d like to invite all the wiki enthusiasts here to go there and give (me) some input.
To be specific I´ve been categorizing some pages but I´m not sure which [category] structure is the easiest to navigate/ most intuitive. So give me some hints please :).

P.S. Don´t do it here though cause I´m too lazy to follow the conversation in two places. You may post the odd 'OK' or 'Will check it out' to keep the thread up top though :D .

I've started going through the wiki editing for grammar, clarity, etc. I suddenly realized that I should probably make sure all this editing I'm doing isn't simply going to be deleted soon what with all the redesigning. So, if someone could tell me what pages are planned to be completely obliterated(or perhaps, what pages are NOT, hehe), it would be much appreciated. It's spring break, but friends are still in school, and thus I currently have a LOT of free time on my hands, don't wanna waste it!

Most every page will stay there, EXCEPT:

Features/Stuff to be overhauled

This includes:
Mapping Format
Unit Scripting Format

Alright, thanks. Didn't want my hard(well, relatively speaking... more like time-consuming :D) work go to waste.