Tuk asked me to take a look at MSDP and I’m starting to go through the list of items he sent me. I’m interested to hear any other requests/issues with the MSDP implementation.
LOCATION updates will be fixed in the next reboot but I have changed the name to CHARACTER_LOCATION in an attempt to standardize future variable names.
The next reboot will also have CHARACTER_EQUIPMENT which should replace the various WEAR_XXX variables. It includes the VNUM, SERIAL (unique item id), and SHORT_DESCRIPTION along with the same information for clasps and runes.
I’ve updated the help file and have started moving older variables to an obsolete list at the bottom to indicate which ones will be going away.
Thanks Teker, my WEAR_WIELD is currently set by the mud as the number 30.
I tried to “remove 30” which the mud replies… “You are not using a ‘30’.”
Any chance you could make the wear/wield/remove commands except the SERIAL number?
The reason for asking is this… say for example I had 4 loops from Iblis, 2 socketted with weapon damage gems and 2 socketted with flail gems… my eqset will need to distinguish the uniqueness when rummaging through my robe amongst the 4 different loops.
Any chance you could add the spell affects of players in the GROUP variable? Would like to detect if players are cursed, webbed, demon bound, deaf etc.
Gorka wrote: ..snip..
Any chance you could make the wear/wield/remove commands except the SERIAL number?
..snip..
- accept
Gorka wrote: Any chance you could make the wear/wield/remove commands except the SERIAL number?
If we were going to build a graphical client with a binary protocol, it would be done. It would be nice to have a simple parser and not be checking for names on everything. I’d prefer not to introduce this into the text commands - it just feels like a half-assed solution.
Quote: The reason for asking is this… say for example I had 4 loops from Iblis, 2 socketted with weapon damage gems and 2 socketted with flail gems… my eqset will need to distinguish the uniqueness when rummaging through my robe amongst the 4 different loops.
I believe the eqset code handles this.
Quote: Any chance you could add the spell affects of players in the GROUP variable? Would like to detect if players are cursed, webbed, demon bound, deaf etc.
I’m not sure what I’m going to do about the GROUP variable. It already has problems with extremely large groups and I don’t like the idea of resending the a lot of the same data over and over. I’ll have to look at what’s in there but it may make sense to split it into 2 parts - one part that only changes with group member changes and another which updates more often.
teker wrote: If we were going to build a graphical client with a binary protocol, it would be done. It would be nice to have a simple parser and not be checking for names on everything. I’d prefer not to introduce this into the text commands - it just feels like a half-assed solution.
Sure, wearing and removing numbers isn’t elegant… what about if socketted gems changed the item names they are socketted to… so for example, I could get loop-tomb-jade from my robe…
Eqset is a solution in most cases, but there are plenty of instances when you just need to get something from your robe, and it’s not to wear it. I’m not sure there is a way to distinguish between multiple items of the same type and the socketted gems currently and if there is, I’d like to know.
Aww, thanks Teker.
Can’t wait to test all the changes