Question on Server... again ...
 

ok, now what I'm trying to do, obviously, is set 10 matches. There has got to be a better way to do this than have 10 different server flags isnt there?

I know I could go reading 10 in the array, and I think to pull it out i'd need a for(), but I tried. I've been out of this for 4 years. Sorry guys.

Yes, you can use a loop instead:

Please note that when defining names for parameters you do not use the temp. prefix to read their values.

Should have known. Forgot to do the if match is i. xD
Like I said, been to long, thanks gambet.

Now, I've seen this in other scripts as well. Just a few questions;
1. Can you explain why the temp. is not required or that just the way it is and I better accept it?
2. Also, does it only apply to temp.variables?
3. Are there any exceptions to this rule? I've noticed that you can use pc[0....10] or whatever to access variables created with temp.pc = player.chat.tokenize();

I meant parameter names with what I stated but it's also true with temp. vars.

If I do this:

I could read the values of foo and bar by just using the words foo and bar without any prefixes (i.e player.chat = foo SPC bar; or so).

Now, with regards to temporary variables, you only need to use the temp. prefix when first defining them and then all other instances after that you don't need to. It's similar to the whole parameter naming I mentioned above where at first you just need to tell the engine that you're defining a temporary variable for the function, once you have defined it, you no longer need to use a prefix to access it.

So:

Of course, you could still use the temp. prefix if you would like but it isn't necessary:

^Would work the same.


This doesn't work with this. vars., since this. vars can be accessed throughout the entire script whereas temp. vars are restricted to the function they are created in.

1) For for() loops, yes.

2) If you mean using a for() loop, no, but in most cases you'll want to unless you plan to loop through an array of things, find something specific, and use the data somewhere else.

3) player.chat.tokenize() separates the player's chat at every space (" ") and put it in an array (tokenize() can also separate at other points by using a string inside the ()). Using that in temp.pc just makes it so you can access that data using temp.pc (needed when defining it) or pc (any time after defining it) and can only be called inside the function it was defined in.
Array sizes start at 0 for the first param and end at the number 1 less than the last param (in normal counting). Params are accessed using [#]. As an example:

I knew how to access function parameters using said defined names. I think I took what you said the wrong way, but thanks for your clarifications. One more question though;

What should I expect this to output?
This? [foo] FOOED [temp.foo] foostring [bar] BARRED [temp.bar] barstring

|| This? [foo] foostring [temp.foo] foostring [bar] barstring [temp.bar] barstring
EDIT to Switch: I know how to access functions and use tokenize; I'm just curious as to how temp. works. I'm glad you told me it's scope is the function it's used in.

EDIT to s^11: Sorry to jack your thread

There's a way better way of doing this... by looping:

I was trying to show how arrays and params worked, not how looping works.

I was showing how looping arrays works... oO?

Ok. The forum I started was for this script.

Now I'm lost, again. Im trying to set it where you can say "startmatches", and it will go through all the set matches, warping the people in for the first one, warp them out when they die, which will cause the 2nd set of matches to start, and warp them in, ect so on and so on.
Im just lost. Don't know where to go next, at all. help :(

probably not supposed to do this but all. bump

Among other things, player.dies is not a variable I am aware of existing. There is a GS1 event called playerdies.

If you plan on using that, it should be in a timeout rather than created so it gets checked more than once.

Your serverside warping functions don't have a player to warp. I believe it is currently warping the NPC itself to another level if it's even being hit.

Take other peoples suggestions from before and create something to clean up the say2, creating a string with a loop.

"if (player.account == serverr.sdematch1[0] " is particularly confusing because you'll only ever warp that particular player in element of the array rather than all the match strings.

NPC Code:

---

function onActionSetMatchServer(match, vplayer, splayer) {

  for (temp.i = 0; temp.i <= 10; temp.i++) {

    if (match == i) makevar("serverr.sdematch" @ i) = {vplayer, splayer};

  }

}

---

Why not this instead:

NPC Code:

---

function onActionSetMatchServer(match, vplayer, splayer) {

  makevar("serverr.sdematch" @ match) = {vplayer, splayer};

}

---

Don't make a loop if you don't have to ;)

This looks even sexier:

NPC Code:

---

function onActionSetMatchServer(i, v, s) serverr.(@"sdematch" @ i) = {v, s};

---

serverr. and server. are the devil though.

Get off my forum :(