RC script flags limit
 

Would it be possible to increase or even remove the limit of characters you can save on a single line in a player's script flags?

At the moment, it's REALLY limiting my development. I'm unable to give myself more than 3 items with RC, because the fourth will be cut off.

How are you storing items?

The variable limit is only on RC not in-game. My chat system, if you load the players attributes in RC, will cut off a large portion of the chat when you save.

It was planned to add edit-player-flags and edit-player-weapons menu item for the RC2 playerlist, can do that sometime soon

clientr.items=proper name,archetype path,quantity

Eh.. so you want to have one huge long list for each item?

Thats a bit.. silly? If you are using archetypes each item should have its own unique index.

clientr.items="Training Sword",weapons/sword/trainingsword,1,"Potion of Life",items/lifepotion,31

clientr.muditem_Training Sword="Training Sword",zod-trainingsword.png,zodsword3.png,...
clientr.muditem_Potion of Life=blah

When you log on or pick up an item, it loads all of your item's variables from the server.
clientr.items is a list of items you have in your possession, it references the systems to the proper string and holds quantity.

Maybe you should store less information in your clientr.items string and more in your clientr.muditem_ strings. Hell, you could even move it all into clientr.muditem_ strings, and then just use getstringkeys("clientr.muditem_") to get all of the muditem strings.

Even if I did, I still have to save the quantity and quantity of each item somewhere.

The muditem_ strings are reloaded at each log on, in case of an update. I'd have to save the quantities elsewhere, regardless. If I do that, I'd have to put the name to go with the quantity.

No matter how you look at it, the length is too limiting

As I said, the length is only for saving attributes in RC.. otherwise I don't believe there is a limit.

On another note, the way I have done things like that in the path is to change the parameters so its like
clientr.item_index=AMMT,itemdata
and when it loads the data, it would just save the value of param[0] in the string already there.. then load clientr.item_index as the value saved on the server.. then add the value of params[0] at the beggining.

Which is the real issue at hand (not the details of a mud system).

I'm with Yen. Updating flags with RC shouldn't cut them off.

Yes, I agree.

This is why I do not use flags on mana realms x_x

Indeed, please fix this.
=^.^=

I'm having this problem with my mudlib system and playerflags too. Way I 'solved' it was remove set attributes from all admins, and made a GuiScript that lets you modify playerflags and such.

Creative :D.

But annoying... :eek:

Indeed that is very creative but you'd have to be on player to set someones attributes. Seems annoying for some people who get lazy such as me. :spam:

:P Lol
I thought of that, too. I think I'm gonna remove attributes from everyone, anyway.

x_x I think its a way better idea to have it all in-game.

Thats how Mana Realms will be.. almost every aspect of the game will HAVE to be changed in-game aside from scripts.. an even that is able to be changed in-game.

If you are too lazy to be on as a player on a pw you work at.. you shouldnt be working there x_x

Theres no reason to NOT be on your player if you are on the pw as staff x_x No staff should be just sitting on RC.

I encourage my staff to use Client-RC as much as possible anyway. My attributes setter and such are attached right on to my Client-RC (along with some other nifty things, like an archetype editor ;)) <3 Client-RC.

Changing RP settings (Items, Descriptions, Topics, Types) is annoying since you have to do it using plain text and it makes it kinda hard to look through after awhile, maybe going to make a GUI for it on player unless we can somehow make plug-ins to RC...