MUDlib

[Angel_Light]

Thanks Invern

[Inverness]

In my mudlib, all items are simply arrays: clientr.mud.item<uniqueid>
Anytime you make an item it gets a unique ID from the
serverr.mud.item.counter, this is so items dont overwrite eachother if you trade or anything like that since you're going to move the whole array.
The most important part of item data is the type which is the first var in array, the type is how you're going to know what stuff is where in the item array. All types are defined in serverr strings so they're easily available.
When you want a variable from an item, such as them name, you use:
mud_getitemvar(itemid, varname);
Or for example, mud_getitemvar("2006","name");

What this does is looks for the item in the clientr strings. When it finds the item, it looks at the item type (index 0) and loads the list of vars from that, and returns the index of the item array that matches the varname's index in the varlist. If you already know the index you simply use:
mud_getitem(id, index);
Any index less than zero returns the whole item array.

For updating the player, when you log in the mudlib compares your items with the archetypes that are loaded into the server, if there is a difference the mudlib updates all the variables except the 'noupdvars' such as the quantity, type, and archetype. Custom items lack an archetype so they're not updated.

[Angel_Light]

so how do we add items to players? Like when they beat a boss or opens a NPC Chest?

[Inverness]

Make a function for it.

I use mud_createitem(archetype, quantity);
Its a public function in the MudItems weapon that can be called clientside or serverside. If you want to call a function from a remote object you have to use:
Object.function(params); = MudItems.mud_createitem(params);

And for that, what I did was make an interface class. Which contains functions that call the function in the weapon object. So if I join the interface class I only have to use mud_createitem() in script and it executes fine.

[Chompy]

My mudlib is different, almost same item setup as yours Inver :]

clientr.mud.item<ID> = { type, quantity, vars};

Type is what to trigger, like weapon, armor, food etc..
quantity is ammount ( obvious) and vars are the variables needed for the type :o

[Twinny]

The mud library vars on Theed can get pretty hectic. Especially for armor. Short format example:

clientr.muditem_16=itemname=Twinny's Test Sword, equiptype= WEAPON_SWORD,weight=2

and so on.

It's done this way so you can load make object with vars from it. Eg.

PHP Code:

temp.mud = new TStaticVar();
temp.mud.loadvarsfromarray(clientr.muditem_16);
echo(temp.mud.itemname); 


The system does have unique identifiers for each number but instead of being stored as a serverr flag, it is stored as a var in a DBNPC npc called 'mudlib'. The mudlib also has functions as well relating to speed/efficiency. Thanks to Kuji, this system is incredibly fast and versatile. But no secrets to give away .

Mud commands can be done via a player class. Eg. player.Mud_CreateItem("sword3", 1); being mudname then quantity.

[ApothiX]

Originally Posted by Twinny

The mud library vars on Theed can get pretty hectic. Especially for armor. Short format example:

clientr.muditem_16=itemname=Twinny's Test Sword, equiptype= WEAPON_SWORD,weight=2

and so on.

It's done this way so you can load make object with vars from it. Eg.

PHP Code:

temp.mud = new TStaticVar();
temp.mud.loadvarsfromarray(clientr.muditem_16);
echo(temp.mud.itemname); 


The system does have unique identifiers for each number but instead of being stored as a serverr flag, it is stored as a var in a DBNPC npc called 'mudlib'. The mudlib also has functions as well relating to speed/efficiency. Thanks to Kuji, this system is incredibly fast and versatile. But no secrets to give away .

Mud commands can be done via a player class. Eg. player.Mud_CreateItem("sword3", 1); being mudname then quantity.

Is your mudlib based on the one I wrote for thamhic? Same var and function names, and methods of storing data, by the looks of it.

[Chompy]

:O I haven't bothered making a mudlib using weight, never found a good algorithm for weight and speed ( movement)

[Twinny]

Originally Posted by ApothiX

Is your mudlib based on the one I wrote for thamhic? Same var and function names, and methods of storing data, by the looks of it.

Kinda similar. Thamhic was used as a reference for the original mudlib but than alot of changes were made in the second version .

Kuji insisted on making all the systems on Theed. I can only touch them after he has finished. To his credit though, the new mudlib is awesome.

However, i find having each var for an item in an array quite ugly. What you could do is have a DBNPC which has items like this
mudlib.sword=itemname=Hax,somevar=hax!
or perhaps an address to a .arc which can be loaded.

Then for players, you could have muditem_2=sword, followed by any modifications/buffs. eg.
muditem_2=sword,+2fire,-50sharpness,+200rust
When accessed, mud function can return either an array of vars or an object containing the vars for use.

If anyone has any questions regarding mud systems, pm my RC on GX. Or forum pm but gx is faster.

If alot of people poke me, I'll write a guide on the wiki and my site. (though still waiting for mysql reset on my site)

Depends what you like though

[Inverness]

I don't like the idea of having the variable names in the array, considering arrays get cut off after a certain point. If I did that I'd make all variable names only 4 characters to limit length.

For weight, I have the function mud_calculate() to parse all the items for values you need, when it gets the total weight it sets that in clientr strings, then the total weight is applied in the movement system somewhere.

I'm still kinda iffy about using Objects for the mud items or anything since I don't know exactly how they work with the server and don't want to spend time trying to find out, its just easier for me to use the function mud_getitemvar() or mud_getitem().

Also on Aeon, because the default Graal Q-Menu is not in use, I renamed all Weapons so simple letter-only names so they don't require quotes or makevar() to be referenced: MudItems, System, SystemGuiFactory, GuiInventory, GuiHud, etc. None of those slashes or anything else, and I love it that way

[ApothiX]

Originally Posted by Twinny

Kinda similar. Thamhic was used as a reference for the original mudlib but than alot of changes were made in the second version .

Kuji insisted on making all the systems on Theed. I can only touch them after he has finished. To his credit though, the new mudlib is awesome.

However, i find having each var for an item in an array quite ugly. What you could do is have a DBNPC which has items like this
mudlib.sword=itemname=Hax,somevar=hax!
or perhaps an address to a .arc which can be loaded.

Then for players, you could have muditem_2=sword, followed by any modifications/buffs. eg.
muditem_2=sword,+2fire,-50sharpness,+200rust
When accessed, mud function can return either an array of vars or an object containing the vars for use.

If anyone has any questions regarding mud systems, pm my RC on GX. Or forum pm but gx is faster.

If alot of people poke me, I'll write a guide on the wiki and my site. (though still waiting for mysql reset on my site)

Depends what you like though

It's uglier when you load the player's attributes, but a lot more organised when you are coding with it :P The architypes in my mudlib were only used as a guide when creating the items. The original plan was to have each item have slightly different stats than others of the same type. Also, the overhead of having to load the archetype file, or access some DB NPC variables would be too much if players had a lot of items.

Originally Posted by Inverness

I don't like the idea of having the variable names in the array, considering arrays get cut off after a certain point. If I did that I'd make all variable names only 4 characters to limit length.

They only get cut off if you use the default RC client to open the player's attributes. Which is why scripted RC is for the win.

Originally Posted by Inverness

I'm still kinda iffy about using Objects for the mud items or anything since I don't know exactly how they work with the server and don't want to spend time trying to find out, its just easier for me to use the function mud_getitemvar() or mud_getitem().

If you take the time to learn them while they are fresh, they will save you more time in the future.

[Inverness]

I really don't see how making the items Objects will help me, I already have a simple way of getting the item data, so if anyone could point this out?

[Admins]

Originally Posted by Inverness

I really don't see how making the items Objects will help me, I already have a simple way of getting the item data, so if anyone could point this out?

Well it's not a big advantage I guess, but such objects can join classes and could do dynamic things. On Graal Kingdoms that is mainly used for illnesses which sit in the inventory of the player and infect other players or npcs or reduce the hitpoints each few seconds or drop some item (e.g. teeth). If such functionality is not needed then you don't need to use TStaticVar.

[Angel_Light]

okay I;m totally lost on this archetype thing, I'm trying to understand but I can't figure out how to add one of my custom to Okies Inventory weapon. :/ Any insight?

[Angel_Light]

*bump*