I like scripting, and I think many players of IRE games spend a fair ammount of time doing it for their respective clients. It would be nice to have an area reserved for it. People could ask questions, get ideas for their own scripts, etc.

Razyx

Lord knows I need all of the help I can get with ZMud

I'd be all for a scripting forum! I read the Achaea scripting forum like an ADD puppy on Speed.

ADD? You don't need speed with some ADD... *hides from Zarguan* scripting is good, I used the stuff from the Noctusari website... *daydream* Just basics, if I can't understand it, I won't use it.

I'm doing okay with scripting... only basic stuff so far but then I'm a programmer so it's not that hard for me to pick up. It's was bloody annoying to get started though. Zmud wasn't exactly intuitive and it was hard to find the list of available commands.

A scripting section would be good. I don't really feel the need for many scripts yet, but if anyone wants some I could try my hand at it.

My most major problem is that I can't get my mind around how to set up herb/elixer balances and a system that won't get spammed out by being locked....usually if I have someone TELLING me in person I can get a hold on things but if anyone thinks they can explain how to set stuff like this up, I'd be grateful.

Heh, I'm useless at this stuff. I do the best I can with JAVA triggers though, so I guess I can't be entirely to blame Having some sort of resource would make it extremely helpful. (and yes, I use JAVA because I did when I first started Achaea and I got attached to it and I'm very obsessive about not changing things ).

Try #help and then go to Index->Reference. That's everything you need




Sit down and analyse how you want to do it, rather than trying to write as you go..

See, I know WHAT I want to do but don't have enough knowledge to do it....

Basically, I want to set up a system that will go in and read when I have an affliction....say I am on fire...well, then it will say---"Yes, you are on fire"---it will then run back and say "Has he cured being on fire?" well, then the answer is no---well, the system will then run over and check ---"Does he have slickness?" If yes, it will repeat the process for slickness, if not, it'll go ahead and heal it.

I think database is the way to go. I'm having issues with 3 things right now. One, I have so many different possibilities of attack, I can't figure out what to name all the aliases, 2, same problem for healing, 3, I know zmudd 5.55 can work with databases or something, its help file are just terrible at it. Because they only seem to want to help you with identify spells.

I want to be able to add and remove items from a database and display them in my status window like Harker's script in Noctusari.org implies. Problem is, I can never get that script to work or anything.

I'm fairly certain that it is going to have to be a database and window combination but I am just too ignorant to pull it off

I haven't had much to do with the database functions of zMud, but for this sort of thing I usually use triggers and variables.
For example: I set up a variable, maybe call it @onfire
Then I set up triggers to set the variable to either true or false, like: "You are on fire" with that causing the value of @onfire to be true and to initiate the the cure. Make another trigger from the cure message "You are no longer on fire" that sets @onfire to false.
Thats sort of the basic idea, unfortunately, I am sort of new to IRE games so I dont know actual trigger messages. Once you have a bunch of affliction variables and triggers to keep them updated you can do all sorts of things, show a list of all afflictions, go through them all and cure any that are true, etc. Of course, balance and equilibrium complicate things a little, but zMud can use multi-state triggers that should be able to overcome this.
Hope this helps in some small way. Like anything, learning with zMud involves a fair bit of trial and error, so always keep backups of important stuff.

I prefer string lists and data record variables for tracking things because of the built-in looping commands provided by zMUD. Instead of having the make some massive alias that checks 100 variables, I can simply #LOOPDB.