deletestring (serverside)
 

It is not working correctly. I said it should delete index 1, but it removed index 0.
Now I have to use this:

NPC Code:

---

      //    deletestring clientr.hats,hatnum;



          setstring temp,;

          for (i=0; i<sarraylen(clientr.hats); i++) {

            if (i != hatnum) addstring temp,#I(clientr.hats,i);

          }

          setstring clientr.hats,#s(temp);

          setstring temp,;

---

I don't know whether it is working clientside/offline.

...you're starting at the highest index and working down, right?
Otherwise you're gonna skip every other index...
Delete 0
Index 1 becomes Index 0, 2 becomes 1, etc.
Delete 1 (formerly index 2...)
Delete 2 (formerly index 4...)

Sorry, what are you talking about?
Do you mean that I used deletestring the wrong way? I didn't even use it in a loop.
Are you talking about the script I am using as replacement? I just copied every thing else into another string.

I am using deletestring for many things and its working, can you post some code example?

I don't want to publish it here.
It is on Classic Developement, Weapons, -System/Trading.

I have put "//" in front of the deletestring command.
The following six lines are what fixed it. (I rescripted the deletestring command).

nice 6 lines :o

What do you mean? I published those six lines in my start post of this thread.

Arg you are using 'temp' ? that will send a lot of data to the player x-x And it still doesnt tell me what should be wrong. A code example of the bug would be good

Oh.. you said the following 6 lines.. but they didn't follow that text.. so :eek: :D

Well, you could always code the server so it does not send data to the client which it cannot read/edit anyways.

Ok, now I am using this.temp, but we are going off-topic here.
Tyhm told me sometime that only LATs are allowed to see the scripts used on Classic, so I won't post it here, but, like I wrote before, you can look at it on Classic Developement, it's in the -System/Trading weapon.
(I tried sending it to you using a PM, but it was 10 times too huge for a forum PM).

However, this is a very short version of it:

NPC Code:

---

if (actionserverside) {

  hatnum = strtofloat(#p(0));

  putnpc2 playerx,playery+2,{join hats;};

  with (npcs[npcscount-1]) {

    this.hat = strtofloat(#I(clientr.hats,hatnum));

    deletestring clientr.hats,hatnum; // <- always delets #0

    callnpc -1,updategani;

  }

}

//#CLIENTSIDE

if (weaponfired) triggeraction 0,0,serverside,DeleteTest,2;

---

No, I meant the following six lines in the script and not in my post.

Variables like those are local to a certain NPC.

They don't start with this., so NO!

And:

NPC Code:

---

  with (npcs[npcscount-1]) {

    this.hat = strtofloat(#I(clientr.hats,hatnum)); // <- this works

    deletestring clientr.hats,hatnum; // <- this doesn't

  }

---

Personally I just wouldn't use a string array, though it depends on how many of each hat you want to allow people to have. If you use ascii() and #K() then you can compact numbers over a fairly large range into a single byte, and then just use a normal string with one character per hat.

Variables like hatnum are local, belonging to the current script, so you can use hatnum like you have written, and it works. You have problems when calling functions of joined classes, because those don't know of the local variables of the other script.

I will update & restart the npcservers on that machine, it seems to be quite buggy (the weapons are not saved).

He is not using classes there, Stefan... :\

Sounds good. But lazy as I am, I'd like Stefan to fix the deletestring command. ;)

Yes, the classes I made are only accessing this.variables when they need data from the main script.
But here I am not calling a joined function. Here it looks like deletestring is always deleting number zero, no matter what I command it to delete.

I will test what happens when I enter a constant number to deletestring. Maybe it is just bugged when using variables. Though I doubt it.

I'm pretty sure he knows that, he's just elaborating. Let's wait and see what happens after the update&restart :)

*reviving the thread*

It's bugged again!!!