serverr flag array trouble

[coreys]

Okay, so I'm making an Events System, and I have the events setup like this:
Theres 4 different event types, each has it's own multidimensional array with the
event names and their data in it. What I'm stuck on is trying to make a list of each event in its category in serverr flags. Ex: serverr.events.contest=Musical Chairs, Emoticons

Now, to spare you with all the for loops and such, here's essentially what I'm trying to do:

PHP Code:

temp.testtype = {"race", "spar"};
temp.elist.race = {{"Foot Race","bla"}, {"Bush Race","bla"}};
temp.elist.spar = {{"Spar","bla"}, {"Classic Spar","bla"};
serverr.events.(@ temp.testtype[0])[0] = temp.elist.(@ temp.testtype[0])[0][0];
serverr.events.(@ temp.testtype[0])[1] = temp.elist.(@ temp.testtype[0])[1][0];
serverr.events.(@ temp.testtype[0])[0] = temp.elist.(@ temp.testtype[1])[0][0];
serverr.events.(@ temp.testtype[0])[1] = temp.elist.(@ temp.testtype[1])[1][0]; 


My problem is that the serverr flags will not set.

[Chompy]

PHP Code:

temp.testtype = {"race", "spar"};
temp.elist.race = {{"Foot Race","bla"}, {"Bush Race","bla"}};
temp.elist.spar = {{"Spar","bla"}, {"Classic Spar","bla"};

serverr.events.(@ temp.testtype[0]) = {};
serverr.events.(@ temp.testtype[0])[0] = temp.elist.(@ temp.testtype[0])[0][0];
serverr.events.(@ temp.testtype[0])[1] = temp.elist.(@ temp.testtype[0])[1][0];

serverr.events.(@ temp.testtype[1]) = {};
serverr.events.(@ temp.testtype[1])[0] = temp.elist.(@ temp.testtype[1])[0][0];
serverr.events.(@ temp.testtype[1])[1] = temp.elist.(@ temp.testtype[1])[1][0]; 


hmm?

I think you need to initialize the array first, for example with {} or new[1]

[dNeonb]

Not releated to the script but to the whole thing. If you make an event system it would be more useful to use a database npc to store all the event informations. If you have many events or long texts it might be a problem.
Yesterday I updated the serverflags on GK Debug because I wanted to add a new tool type. But I was not able to add it, the limit of variables in the serverflags was reached.

Think about it.

[xXziroXx]

First of all, let me just tell you that Bjorn is right. Use a DB instead of serverr. strings. Now to answer your question..

Originally Posted by Chompy

I think you need to initialize the array first, for example with {} or new[1]

Indeed. You cant edit a part of an array that doesnt exist.

serverr.flag = new[5];
serverr.flag[2] = "lol";

Just an example on how to do it before you set the data.

[Horrified]

Originally Posted by dNeonb

But I was not able to add it, the limit of variables in the serverflags was reached.

Uh sorry but, do you know the exact limit?

[Inverness]

Originally Posted by Horrified

Uh sorry but, do you know the exact limit?

The limit is in the RC's editing window itself not the actual server flags. The limit is most likely 255 characters.

[Chompy]

Originally Posted by Inverness

The limit is in the RC's editing window itself not the actual server flags. The limit is most likely 255 characters.

Yep, and it should be removed as you stated in that other thread..

[coreys]

Originally Posted by dNeonb

Not releated to the script but to the whole thing. If you make an event system it would be more useful to use a database npc to store all the event informations. If you have many events or long texts it might be a problem.
Yesterday I updated the serverflags on GK Debug because I wanted to add a new tool type. But I was not able to add it, the limit of variables in the serverflags was reached.

Think about it.

...I am using a database npc. I'm trying to set serverr flags so that my event tool doesn't have to do 436263 triggers.

[Inverness]

I believe Database NPCs are a bit unsafe for information thats not set in the script since if its in flags only it could be cleared on reset.

For things like that I use TStaticVars that save to file.

By the way, there is a serveroption that limits you to only changing existing server flags rather than being able to create new ones, make sure thats not enabled?

Originally Posted by coreys

...I am using a database npc. I'm trying to set serverr flags so that my event tool doesn't have to do 436263 triggers.

Like Ziro said, the array has to be existing before you can edit an index of it, though it is possible to add to non-existant arrays since it will just create one if there isn't one existing.

PHP Code:

serverr.events.(@ temp.testtype[0]) = new [2];
serverr.events.(@ temp.testtype[0])[0] = temp.elist.(@ temp.testtype[0])[0][0];
serverr.events.(@ temp.testtype[0])[1] = temp.elist.(@ temp.testtype[0])[1][0];
//OR
serverr.events.(@ temp.testtype[0]) = {
  temp.elist.(@ temp.testtype[0])[0][0],
  temp.elist.(@ temp.testtype[0])[1][0]
}; 


Use the second one

Originally Posted by Chompy

I think you need to initialize the array first, for example with {} or new[1]

You still can't edit index 1 as you did in your code because it doesn't exist, only index 0.

[zokemon]

I personally use database npcs that backup data to a file on update. This uses the least gserver usage (HD usage) in most cases where you don't need to update much.

About editing array members that do not yet exist, make your own function if you want that simply array.add()'s if the array.size() < the member you want to edit (or so).

[coreys]

Chompy helped me make it work. Just used new[]...although, for whatever reason new[] didn't work for me before, in the same exact script.

[Chompy]

Originally Posted by Inverness

You still can't edit index 1 as you did in your code because it doesn't exist, only index 0.

I forgot new[] indexes start at 1 xD

But Vash, I would suggest what Inver told ya to do:

Originally Posted by Inverness

PHP Code:

serverr.events.(@ temp.testtype[0]) = {
  temp.elist.(@ temp.testtype[0])[0][0],
  temp.elist.(@ temp.testtype[0])[1][0]
}; 


But that's if you know the size ;o

[zokemon]

new[i] is such where i is the count, not an index.

It's kind of like doing:
var.count() = i;

Of course the syntax for that is completely wrong and such a thing is impossible.

[MysticalDragon]

try databases serverr flags dont use arrays anyway

[Skyld]

Originally Posted by MysticalDragon

try databases serverr flags dont use arrays anyway

You can use arrays in serverr. variables because the Graal engine treats arrays as specially delimited strings; they are not a distinctive datatype in terms of storage.

[coreys]

Originally Posted by Skyld

You can use arrays in serverr. variables because the Graal engine treats arrays as specially delimited strings; they are not a distinctive datatype in terms of storage.

:o
inteereestiiinggggg

But I already knew arrays worked in serverr flags anyways, they have for as long as I can remember.

[Relinquish]

serverr flags should not be used, at all, there are bugs in the communication of them from server -> client.
The server seems to randomly forget to send some clients the updated variable, or forgets to send the variable period, which leads to some massive problems.

[Chompy]

Originally Posted by Relinquish

serverr flags should not be used, at all, there are bugs in the communication of them from server -> client.
The server seems to randomly forget to send some clients the updated variable, or forgets to send the variable period, which leads to some massive problems.

What? What are you talking about? O.o

[Relinquish]

If you're on a populated server and change a serverr string a lot, and then have each player echo what they read it as each time it's changed, some of the players will eventually start echo'ing what an old string was, since the server didn't send them the updated string properly.

[coreys]

Originally Posted by Relinquish

If you're on a populated server and change a serverr string a lot, and then have each player echo what they read it as each time it's changed, some of the players will eventually start echo'ing what an old string was, since the server didn't send them the updated string properly.

Or whatever server you're doing this on is fsked, 'cause I've never had this problem o.0

[xXziroXx]

Originally Posted by Relinquish

If you're on a populated server and change a serverr string a lot, and then have each player echo what they read it as each time it's changed, some of the players will eventually start echo'ing what an old string was, since the server didn't send them the updated string properly.

I dont know about the problem you speak of, never encountered it on Zodiac or Maloria.