40oz
 Official Sponsor
Joined: 03 January 2004
Posts: 1799
|
17 March 2007 19:48 (UK time)
hmm. It looks kinda messed up. Make sure before every action you have an event trigger to trigger those actions. Here are all possible Event triggers:
void OnMapStart()
void OnObjectHurt_???()
void OnObjectDie_???()
void OnWaypointReached_???(int ObjectId)
void OnEnterVehicle_???()
void OnExitVehicle_???()
void OnObjectTypeEnter( int ObjectId, int ObjectTypeNumber)
It took me a while to figure out how this scripting stuff works, but I finally got the hang of it. So if you can do me a favor and describe what exactly you are trying to make happen, I can help you out a bit.
M2 currently doesn't do a good job at describing what is wrong with your scripts. It's especially annoying when things such as typos can disable your whole script file.
If you are not sure how scripting stuff works, I can explain the skeleton of it for you:
At the beginning of every script, it should always start with a heading like this:
#title "whatever your mapname is"
#author "whatever your name is"
#include meteor2
After that, you gotta place an event, such as those listed above. Events are things that happen that causes functions to go in effect. It has to be exact spelling, including caps, and any question marks have to be filled in with whatever is necessary. The script names are pretty self explanatory for what they do. (void OnObjectDie_???() means that the following functions start when ??? object ID dies.) Immediately after placing whatever event, and filling in the missing information, start a new line, and type in the functions you want to happen. You can have multiple functions for one event, though each function must be seperated to be in their own lines, and also seperated with a semicolon (this thing '';'') at the end of every function. I see you already know that though. However, once you have entered in your functions for the event, they must be enclosed in {}'s. Those should also be in seperate lines.
By now your event/functions should look like this. (remember that your heading is required at the top too.)
[whatever event you choose]()
{
[whatever function you choose];
}
Or if you have multible functions:
[whatever event you choose]()
{
[whatever function you choose 1];
[whatever function you choose 2];
[whatever function you choose 3];
}
After you enclose your actions, you can start a new event, and open up more functions by enclosing them in {}'s.
After you have finished making all your events an the functions that take place in them, make sure you tack down all the events that are used in the line after your heading. I'm not completely sure why you need this, but it's required to make your scripts work. simply all you do is type this:
export [your third event listed];
export [your second event listed];
export [your third event listed;
Remember to fit that in immediately after your heading after you had finished typing in all your events/functions. Like functions, they also must be seperated in seperate lines and with semicolons. It is also possible to produce an entire script file with no spaces or tabs. In fact it's more likely to work correctly without them.
Also those double slash things (//[whatever text]) are not required. They are simply little notes that describe what your event/functions do in your map in english. I tend to avoid them so that I dont confuse myself or disorganize my scripts.
I described the skeleton of script files the best I could. I hope it made sense, because I knew when people tried to describe to me how to make a script file, I couldnt understand it for the longest time. Once you understand the whole thing, you can pump out script files with ease.
I'd still like to continue helping you with your script though, mind telling me what youre trying to make happen?
*Papercut
Pro-Murder.
Legalize Crime. |
Edited: 17 March 2007 19:49
You need to login to create posts in this thread.
|
my tip is to make the objects placing as much independent as possible, for example: If it disapears, the level wont be lost :S or something 
;
