RC: Chests

[Deadly_Killer]

Originally Posted by Inverness

Uh, yes it can, just use triggeraction(). The shape needs to be set on both sides.

No, you can't triggeraction to itself on server, so the client receives it.

[Inverness]

Hmm, there are other ways besides triggeraction().

Though, I suppose, with a chests system, if you really have 5000 then its best to have all data pre-loaded and only call server to flip things. Save your chest information to a variable on the clientside, not text file.

Text File = Hard Drive, Variable = RAM.

It can't be saved to a client variable for obvious reasons. Use something like player.chests

[Deadly_Killer]

Originally Posted by Inverness

Hmm, there are other ways besides triggeraction().

Though, I suppose, with a chests system, if you really have 5000 then its best to have all data pre-loaded and only call server to flip things. Save your chest information to a variable on the clientside, not text file.

Text File = Hard Drive, Variable = RAM.

It can't be saved to a client variable for obvious reasons. Use something like player.chests

If you can't handle 4-5 mb (at tops.. ever), then.. yeah <.<.

[DustyPorViva]

Even a mb for just chests seems a little excessive.
If you're worried about an array not being accessible, maybe create a quick GUI to edit people's chests and such?

[Deadly_Killer]

2 kb = 5-6 chests already.

It isn't nothing big, a body is like a mb btw.

[Inverness]

Save that data into a clientside var, don't need large file loading everytime I change level.

[Deadly_Killer]

clientside var.

hm, I could.

do you mean something like:

Load an array called playerchests? ( so it doesnt show in attr? )

[Inverness]

You should save all chest-related information in an array called player.chests on the clientside. It would be cleared on logout so you would need to have it sent to client on login and make sure you save any changes to server.

[Deadly_Killer]

Hm, and it could be of any size :o?

[Inverness]

I have yet to find a limit on array sizes, as long as the array is only read by script and not displayed like client flags or dbnpc flags then it should be fine. You can allocate arrays in programming of any size as long as you have the memory to store the data.

[Deadly_Killer]

Originally Posted by Inverness

I have yet to find a limit on array sizes, as long as the array is only read by script and not displayed like client flags or dbnpc flags then it should be fine. You can allocate arrays in programming of any size as long as you have the memory to store the data.

Thanks, I will change this soon. =D.

rep++

[zokemon]

Originally Posted by Inverness

I have yet to find a limit on array sizes, as long as the array is only read by script and not displayed like client flags or dbnpc flags then it should be fine. You can allocate arrays in programming of any size as long as you have the memory to store the data.

Actually, you can put any size into a client. and clientr. variable (or any variable stored on the player's /open for that matter) but it will trim the variable when ever you edit the player using /open on RC. My solution: script your own custom /open ;o

[Inverness]

Originally Posted by zokemon

Actually, you can put any size into a client. and clientr. variable (or any variable stored on the player's /open for that matter) but it will trim the variable when ever you edit the player using /open on RC. My solution: script your own custom /open ;o

I know this, however /open is used frequently so it cant even be considered for the large arrays.

We cant script for custom RC now can we? Stefan should fix this problem.

[zokemon]

Originally Posted by Inverness

I know this, however /open is used frequently so it cant even be considered for the large arrays.

We cant script for custom RC now can we? Stefan should fix this problem.

I already have.

[MrAnonymous_P2P]

So..........what is the purpose of all this?

[Deadly_Killer]

Originally Posted by MrAnonymous_P2P

So..........what is the purpose of all this?

What is the purpose of this post?