Alright, Palisade is great. But I was wondering if anyone knew how I could remove the "if on balance then stand" thing, because I got springup, and do not need balance to stand anymore.

Suggestions? Theories? Rack of Lamb?

Well, for a first, you can try to just put springup in the stand variable instead of the standcommand itself, and then add the trigger for when you springup and put what is in the "You stand up and blah" trigger in that one.

EDIT: Good for a first try, at least.

Did that, still waits for balance.

I just need to figure what I need to remove or change so it'll stand while I'm off balance.

delete the balance check in able_stand and scan_stand or whatever it's called. And always keep a backup!

Backup? Psh, who does that?

I've learned more about Palisade by destroying it and having to re-fix it than I ever would have if I kept backups!

Delete the balance check in the able_stand function, and any other restrictions that don't apply to springup, if any. I think that if you have one broken leg, you can still springup, but I might be terribly wrong. Then search for whatever cure for prone he uses, I think you will find that in the scan_balance alias. It will check for prone at the prompt, I don't think you need to add any triggers.

You'll need to move the checks from i_scan_balance to i_scan_general, too, and change the balance_affs and general_affs to move the prone affliction. Not sure if that's all you'd need or not.

Holy hell, batman.. Better save the changes I've made so far..

I'll try it and let you all know what happens

I totally wrecked everything Syntax error when I tried pasting the crap from balance to general, I have no idea how to make it work

he %db( @writhe_cures, %i) #if (@able_scan and !%iskey( @afflictions, aeon) and !%iskey( @afflictions, sap) and @balanced == 1) {
^ argument expected

wtf is it trying to tell me?


Here's the trainwreck.. I keep trying to fix it, but it only gets worse! Starting over.

Now its back to a Syntax error with #if (!%iskey( @flags, writhing))

You're missing a brace, semi-colon, or some similar thing. Those aliases are very complex, so pasting in the wrong place can completely goof them up, as you've noticed. I never work on these things directly in the settings editor myself. I do all my work on a text editor and then import the script. You could at least work on the code in a text editor, making sure you've got the right scope (braces and all) before pasting it back into the settings editor...