Please help finish my script
 

Ok I need my script so it will always be active

//#CLIENTSIDE
if (weaponfired) {
for (i=1;i!=0;i++) {
playermp=i*1;
sleep .95;
}}

Thats what I got

This should be in the GS1 area really. But, use a timeout.

uh can u show me im so confsued

If you're so confused, start with something easier.
And "Please help finish my script"? Bad title. No we will not help you finish it. If you want us to help you understand it, sure.
This is what you have so far:

A timeout:

NPC Code:

---

if (timeout) {

  timeout = #;  // Replace # with a number

}

---

***** @ i*1;

Just by looking at what you're doing, it looks like you're trying to make a sliding effect. That would look like this:

NPC Code:

---

//#CLIENTSIDE

if (weaponfired) {

  for (i=playermp;i<100;i++) {

    sleep 0.1;

    playermp=i;

  }

}

---

But in your case, you probably want to do this:

NPC Code:

---

//#CLIENTSIDE

if (created) timeout = 0.05;



if (timeout) {

  playermp = 100;

  timeout = 0.05;

}

---

//#CLIENTSIDE
if (created) {
timeout = 0.05;
}


if (timeout) {
playermp = 100;
timeout = 0.05;
}

-_- Use brackets right

playermp cannot be set clientside. You had might as well do something like this on the serverside:

You don't need brackets after the if (created). I normally do the same when it's just one command following the statement. i.e.
Adding brackets to just one line when it's already easily understood is just a waste of time and space.

Meh, it looks better Zelph. ;o Also you use a triggeraction on the clientside to server for the MP

It's quite inefficient to send however many triggeractions from the clientside, when you could just run the operation serverside.

I'm currently wondering why you've chosen to use the timeout feature.
A 'for()' loop works the same...?

A for () loop needs an initiator, making it just as easy to use a timeout.

All... hail... Skyld... o.o;

anyways... He might have some clientside only actions or stuff of the such. That's why suggested that.

On the subject of triggeractions, couldn't you locate a function above the //#CLIENTSIDE statement and when called, it would run serverside?