I disagree - The Millisecs() function should run consistently enough on all computers
You are completely missing the point. Every bot gets an equal chance to execute it's AI, irrelevant of the actual time that it takes the computer to process it.We DONT NEED MilliSecs(). The clock is based on a sort of turn-based gameplay. This isn't a real-time program. Basing our clock function on real time would mess it up. Not every computer executes code, or renders the screen at the same speed.
Looking at the DrawText function, would I just have to replace
You can use the DrawText command like so:thisText.TypeText = DrawText("P r e s e n t i n g t h e c o m p e t i t o r s . . .", 0, 0) thisText\TextID = StandardTextThe reason the return value is saved in a TypeText variable is so that we can assign it an ID, like you see in the example above. The reason for the ID, is so that if we run through the TypeText Type list using a For Each loop, we can identify which texts are solo (StandardText), or part of the bots banner (BotBanner) or stats display(BotStat). This way, if we, say, wanted to erase all texts on the screen, we could do so without upsetting any of the texts that are associated with the bots.
EDIT:You know, looking back on this, I should have just set StandardText to 0. That would eliminate the step of having to assign the ID to at least the standard texts. I may make that change...
Also, if we wanted to Show/Hide the text, or change it's ID, or just delete it entirely, we can do so through that variable.
Unlike the normal Text command though, these texts stay visible on the screen even after screen refresh (since they are 3D objects), so you don't have to keep 'redrawing' them to the sceen every game loop. Your code (or SOME code somewhere) will have to delete them when they are no longer needed.
the coding conventions...I personally think they can cripple the flow of the project if adhered to strictly
having the convention will help make writing the documentation easier
They do more than just help write the documentation...They also help people to understand the code that's already been written since all the code in every file is written in the same style.
For instance, in the coding convention, it states that all Constants, Globals, Arrays, Types, Functions, and Labels (basically everything that's globally accessible) is Capitalized. All local variables start with a lowercase character.
This one convention alone, helps people to quickly see which identifiers used in the code are Global or Local (which quickly tells them where they can find those identifiers elsewhere, meaning either within the same function or outside of the function).
I'll correct any inconsistencies later on.
Trust me, that will never happen...Do it from the start, so it's done.
BTW, you aren't really serious about a few of those sounds are you? I mean the WHOOSH.WAV sound for MissileDetonate and MineDetonate???