NEXUS queueing

by Thalos

Back to Mechanic's Corner.

Thalos2008-04-24 17:41:57
So the adventure into building a system continues.
I understand how the concept of the queue works, its the whole coding of it that I'm sketchy on. The main thing I'm trying to do right now is make something that once I start writhing or focusing it wont do it again until it finishes.
As always any help is greatly appreicated
Kiradawea2008-04-24 18:34:36
I'd suggest that you create a variable. Let's call it "writhe", you can now use this so that whenever you writhe, this variable will change, and when you're finished writhing, it will change back.

Now, let us make a reflex for when you are webbed. In the reflex, you first make sure to check the variable for "writhe". That way, you'll know if you are already writhing or not before you continue.

Well, that wasn't very good at explaining... I'll try to make an example since I've been meaning too. Just never gotten around to actually doing it.
Bashara2008-04-24 20:07:29
That's actually most likely the easiest way to do it with Nexus, even if by the time you finish coding a full system you'll have as many variables as you do triggers.

Anyway, Kira's suggestion to use variables is great. It's also partially how I forged my own Nexus Forging system from scratch. Was about to post it, but random curiosity came over me, I did a search for NEXUS FORGING, and found out that Rika had already beaten me to it.

Not to be redundant, but BOLLOCKS
V(see below)V



*Edit*
P.S.: I've changed it since then and slimed it down
to more than half of what it used to be. Bare bones
skeleton it is now, no frills, but I like it better.
P.S.S.: If someone doesn't beat me to it, I'll try to
make a post later about how I'd go about it. And
by 'later', I mean when I regain a level of functioning
awareness near normal human levels.
Kiradawea2008-04-25 21:48:52
Okay, I've been tinkering a bit, and while I haven't gotten the chance to test it, here's what I've begun with that might be of help.

First, I have created the Variable Writhing. Should be pretty self-explanatory.

Next, I've added these triggers.

---"You have writhed free of your entanglement."

---#SET Writhing 1

and

---"You begin to struggle free of your entanglement."

---#SET Writhing 0

Finally,

---"Sticky strands of webbing spray out from {w} to cover you."

---#IF $writhing {writhe}

That SHOULD work... I think. I haven't tested it yet though. Need someone who can entangle me first.

Bashara2008-04-26 06:18:32
*Edit*
I completely forgot that a variable being used a condition in a trigger, alias, or keybind is supposed to be written as $variable. Edit is being made ASAP!

*Edit*
I hope I got all the trigger variables. I'm not operating at 100% right now, so I could've missed one. I'll recheck again.


You're definitely on the right track, but this will probably work better.


CODE
VARIABLES

Variable: writhe
Variable: restricted
Variable: balance


WRITHING TRIGGERS

Trigger: You have recovered balance
#set balance = yes
#echo {*****BALANCE RECOVERED*****} {*****BALANCE RECOVERED*****}
#if $restricted = yes {
#if $writhe = no {
writhe
}
}

Trigger: {<}You begin to writhe helplessly, throwing your body off balance.{>}
#set restricted = no
#set writhe = no

Trigger: You have writhed free
#set writhe = no
#set restricted = no
#echo {*****WRITHE SUCCESSFUL*****} {*****WRITHE SUCCESSFUL*****}

Trigger: you manage to writhe yourself free
#set writhe = no
#set restricted = no
#echo {*****WRITHE SUCCESSFUL*****} {*****WRITHE SUCCESSFUL*****}

Trigger: You begin to struggle free
#set writhe = writhing
#echo {*****WRITHING IN PROCESS*****} {*****WRITHING IN PROCESS*****}

Trigger: You begin to writhe furiously to escape the antlers
#set writhe = writhing
#echo {*****WRITHING IN PROCESS*****} {*****WRITHING IN PROCESS*****}

Trigger: jerk as the iron cross pulls your limbs
#set writhe = writhing
#echo {*****WRITHING IN PROCESS*****} {*****WRITHING IN PROCESS*****}


TRIGGERS THAT CAUSE RESTRICTION

Trigger: Sticky strands of webbing spray out from {w} to cover you
#set restricted = yes
#echo {*****YOU ARE ENTANGLED*****}
#if $balance = yes {
writhe
} else {
#echo {*****YOU ARE OFF BALANCE*****} {*****YOU MUST WRITHE*****}
}

Trigger: Tight bindings cling to you
#set restricted = yes
#echo {*****YOU ARE ENTANGLED*****}
#if $balance = yes {
writhe
} else {
#echo {*****YOU ARE OFF BALANCE*****} {*****YOU MUST WRITHE*****}
}

Trigger: you are impaled viciously
#set restricted = yes
#echo {*****YOU ARE IMPALED*****}
#if $balance = yes {
writhe
} else {
#echo {*****YOU ARE OFF BALANCE*****} {*****YOU MUST WRITHE*****}
}

Trigger: think of nothing but freeing your impaled foot
#set restricted = yes
#echo {*****YOU ARE STILL IMPALED*****}
#if $balance = yes {
writhe
} else {
#echo {*****YOU ARE OFF BALANCE*****} {*****YOU MUST WRITHE*****}
}

Trigger: your impaled body shudders on the end of the weapon
#set restricted = yes
#echo {*****YOU ARE STILL IMPALED*****}
#if $balance = yes {
writhe
} else {
#echo {*****YOU ARE OFF BALANCE*****} {*****YOU MUST WRITHE*****}
}

Trigger: are impaled and must writhe off
#set restricted = yes
#echo {*****YOU ARE STILL IMPALED*****}
#if $balance = yes {
writhe
} else {
#echo {*****YOU ARE OFF BALANCE*****} {*****YOU MUST WRITHE*****}
}

Trigger: Your health continues to drain away as your impaled body shudders
#set restricted = yes
#echo {*****YOU ARE STILL IMPALED*****}
#if $balance = yes {
writhe
} else {
#echo {*****YOU ARE OFF BALANCE*****} {*****YOU MUST WRITHE*****}
}

Trigger: You are impaled, which makes movement
#set restricted = yes
#echo {*****YOU ARE STILL IMPALED*****}
#if $balance = yes {
writhe
} else {
#echo {*****YOU ARE OFF BALANCE*****} {*****YOU MUST WRITHE*****}
}

Trigger: Vicious spikes slam into your flesh and nail you
#set restricted = yes
#echo {*****YOU ARE CRUCIFIED*****}
#if $balance = yes {
writhe
} else {
#echo {*****YOU ARE OFF BALANCE*****} {*****YOU MUST WRITHE*****}
}

Trigger: You bleed like a stuck pig
#set restricted = yes
#echo {*****YOU ARE CRUCIFIED*****}
#if $balance = yes {
writhe
} else {
#echo {*****YOU ARE OFF BALANCE*****} {*****YOU MUST WRITHE*****}
}

Trigger: the image of the Hanged Man on it at you
#set restricted = yes
#echo {*****YOU ARE RESTRICTED*****}
#if $balance = yes {
writhe
} else {
#echo {*****YOU ARE OFF BALANCE*****} {*****YOU MUST WRITHE*****}
}

Trigger: bound and tied
#set restricted = yes
#echo {*****YOU ARE RESTRICTED*****}
#if $balance = yes {
writhe
} else {
#echo {*****YOU ARE OFF BALANCE*****} {*****YOU MUST WRITHE*****}
}




Okay. As you can see, I listed as many affliction lines for restriction, impale, and whateverelsethereis as I know of. Partially because I wanted you to know them if you didn't already, and partially because I haven't gotten around to it myself sad.gif

-You'll notice that the trigger lines are much shorter than what most other people use. Reason for this is because it's my experience that Nexus is not friendly to capital letters, periods, and newlines in its triggers. Sometimes they work, sometimes they don't, and I like to play it safe.

-You'll also notice that I use words instead of numerical values for my variables. This is because, again, in my personal experience, sometimes numerical values just don't work. Now, this could be because back when I did use numerical triggers, I was simply stumbling my way around, learning by experience how to code in Nexus script. However, worded values have worked for me so far, so that's what I use.

-The reason for the {*****x*****} echoes is because I find combat to insanely fast paced for my liking, especially if it's one of those cluster f-censor.gif-s that is multiplayer combat, IE: more than four people. I use echoes so that instead of having to try to decipher the (wonderfully written) text that goes along with the skills and attacks of Lusternia, I can simply read the echoes for the gist of wtf is going on and be done with it. It's up to you whether or not to actually use them, it's just what makes things easier for me. I'm the son of an engineer and am somewhat of an engineer at heart, and engineer and mathematicians will always find a way to make things easier because we're lazy children of Bast.

-I hope it works for you, I haven't exactly had the chance to test all of these myself, and now I'm wishing that I'd done this in XML so you could simply copy+paste them into Import and be done with it, but I'll get around to it when I have the chance to code and test them so I can be sure.

I don't have any monk triggers because I can't find them, and the list I have is actually largely incomplete of a lot of things, so I apologize for that.

I hope I did this right, that you find it easy to follow, and that it helps. If someone more knowledgeable about Nexus scripting would like to review it and make any corrections, point out anything I missed, or offer any suggestions on streamlining, please do. It'll only help us all happy.gif


More affliction lines:
{<}Turning her backside to you, a {*} rears up on her front legs and
covers you with a spray of sticky webbing.{>}

wrapping you in a cocoon of slime.{>}

{<}Twisting around, a giant black widow spurts sticky strands of web at you from the spinners on her abdomen.{>}
Rika2008-04-26 06:41:57
Also, use {<} and {>} where appropriate. Just speeds things up (and won't get you killed if someone illusions a huge range of afflictions in one line)

In case you don't know when to use them, {<} is used for triggers that you want to fire only when it comes in a new line. {>} is for when you only want it to fire if the trigger ends a line.

For example:

{<}Sticky strands of webbing spray out from {w} to cover you.{>}

This will fire on:
Sticky strands of webbing spray out from Bob to cover you.

But not on:
You bleed 50000000 health Sticky strands of webbing spray out from Bob to cover you You have been slain by Bob
Bashara2008-04-26 06:51:48
I never thought of that blink.gif

Thanks, Rika. I'll have to experiment with that.
Rika2008-04-26 07:17:18
QUOTE(Bashara @ Apr 26 2008, 06:51 PM) 506211
I never thought of that blink.gif

Thanks, Rika. I'll have to experiment with that.


But that's like the most basic Nexus command beyond #if, #set, {w} and {*}.
Bashara2008-04-26 07:43:22
When I was starting out, I could never get {w} and {*} triggers to work right, so I've never really used them and just stuck to using the exact wording. I didn't even figure out how to make an #if statement until two months ago confused.gif
Rika2008-04-26 07:47:06
QUOTE(Bashara @ Apr 26 2008, 07:43 PM) 506229
When I was starting out, I could never get {w} and {*} triggers to work right, so I've never really used them and just stuck to using the exact wording. I didn't even figure out how to make an #if statement until two months ago confused.gif


If you read the Nexus documentation a few times, you should be understand most of its functions. I'm a scripting noob, so it took me a few reads to get it right too. But if you need any help, let me know. I don't use Nexus anymore, but I still remember how to work most things on it (not really saying much tongue.gif). happy.gif
Bashara2008-04-26 07:59:15
I definitely need help, I've read about 90% of the help site and understood about 75% of that unsure.gif

I've been experimenting with different clients that will work for Mac, but so far I'm having trouble adjust to them and their scripting language. Nexus has similarities, but it's kind of unique.
Thalos2008-04-26 14:02:21
Appreciate all the help. Thanks a ton, Bash, that actually makes a lot of sense and was what I was hoping for.

You raise an interesting point with the {<} and {>}, Rika. Would you happen to remember if those'd work in the middle of a trigger, if say its more than one line long?
Rika2008-04-26 20:46:38
I don't recall ever using them in the middle of a trigger like that, but it is worth a try. Nexus wordwrapping sucks.
Bashara2008-04-26 21:38:04
QUOTE(thalos @ Apr 26 2008, 02:02 PM) 506274
Thanks a ton, Bash


Aww, shucks blush.gif

QUOTE(thalos @ Apr 26 2008, 02:02 PM) 506274
You raise an interesting point with the {<} and {>}, Rika. Would you happen to remember if those'd work in the middle of a trigger, if say its more than one line long?



I'm not sure, either, but as soon as my chem final is over, I'll find out. Also, I'm working on converting those writhe triggers into XML format, but I'm gonna collect some various lines from mobs who cause restriction, IE: thorn beasts, kephera, etc.
Bashara2008-04-27 11:45:46
A few more affliction lines have been added to the end of my code post. Just use the same script for the rest of the writhe triggers.

Also, one thing I should mention: I haven't found a perfect way to prevent executing commands that require your character to be unrestricted while you're writhing.

If you continue to spam an action that requires you to be free of restrictions, you will never complete your writhe and be stuck in an endless loop. I'd advise against using triggers to automatically execute commands and just wait patiently for your character to complete the writhe.

Doing most of the triggers one by one. I can't really test all of them because that would require getting some other people to help me, and the server's kinda dead right now unsure.gif

Either way, I'll soon have this little mini-system in XML format, which I'll post as a url instead of another long code box.


*****IMPORTANT*****


I discovered a really bad potential loop just a few minutes ago while gathering the lines and testing for flaws. If for some reason restricted gets set to yes, but you're not actually restricted, you will continuously throw yourself off balance, recover balance, then throw yourself off balance again, repeat. A trigger to prevent this loop from happening has been added near the top of the list of the Writhing Triggers section:
CODE
{<}You begin to writhe helplessly, throwing your body off balance.{>}


The trigger has been thoroughly tested and will stop the loop if it occurs.
Kiradawea2008-04-29 14:18:40
Very well done Bashara. I've added your triggers to mine, and though I generally prefer highlights, I'll be using this as a chance to test how Echo works compared to Highlight.

Anyway, I have a few other writhe triggers in my curelist, so I'll add them here for you.

QUOTE
Trigger: A blue-ringed octopus grabs you with multiple tentacles until you can no longer
#set restricted = yes
#echo {*****YOU ARE RESTRICTED*****}
#if $balance = yes {
writhe
} else {
#echo {*****YOU ARE OFF BALANCE*****} {*****YOU MUST WRITHE*****}
}

Trigger: A large yellow spider rears up
#set restricted = yes
#echo {*****YOU ARE RESTRICTED*****}
#if $balance = yes {
writhe
} else {
#echo {*****YOU ARE OFF BALANCE*****} {*****YOU MUST WRITHE*****}
}

Trigger: A monstrous nagameth wraps his tail about you and squeezes tightly
#set restricted = yes
#echo {*****YOU ARE RESTRICTED*****}
#if $balance = yes {
writhe
} else {
#echo {*****YOU ARE OFF BALANCE*****} {*****YOU MUST WRITHE*****}
}

Trigger: A peep soldier whips you with a length of red licorice, which wraps around you.
#set restricted = yes
#echo {*****YOU ARE RESTRICTED*****}
#if $balance = yes {
writhe
} else {
#echo {*****YOU ARE OFF BALANCE*****} {*****YOU MUST WRITHE*****}
}

Hopefully this will be of some use.
Bashara2008-05-23 03:31:04
Script for Vine from druids:

CODE
writhe
    writhe


However, after some fiddling, I came up with this:
CODE
writhe


The second trigger is universal and will work regardless of which weapon the druid points at you.


As for the {<}{>} suggestion in order to turn multi-line triggers into single groups, it just doesn't work. I've tried it at least 10 different ways, using selective parts of script, but Nexus doesn't seem to accept it.

I do have a solution, albeit a temporary one. We all know that Nexus is a single window that cannot be enlarged to allow for longer word wrapping. However, it is possible to open the Options tab, turn your font size to 8 or 9, and CONFIG WRAPWIDTH 110. By doing this, you reduce a large majority of what would potentially be multi-line script into 1-2 lines that contain the information for your system to differentiate between you and someone else being afflicted.

110 seems to be almost exactly perfect to fit inside the window when the text is size 8-9. I know that this turns the text into an unreadable jumble. But honestly, when I finally code my system and work all the kinks out, it won't matter if I can read the text or not because the system will take care of everything, and I will have included echoes to let me know if I'm getting sleep/slit/whatever locked so that I can use manual commands to cure myself out of it. Unless someone else can figure out how to code multi-line triggers, that's my temporary solution. I haven't combat tested it yet, and won't until I'm fairly sure I can operate well in that kind of environment, but it's all I can come up with at the moment.
Rika2008-05-23 10:51:08
I just made wrapwidth 255 (ie no wrap) for when I needed debating triggers.
Aidyn2008-06-13 13:52:46
QUOTE(Bashara @ Apr 27 2008, 02:45 PM) 506602
Also, one thing I should mention: I haven't found a perfect way to prevent executing commands that require your character to be unrestricted while you're writhing.

If you continue to spam an action that requires you to be free of restrictions, you will never complete your writhe and be stuck in an endless loop. I'd advise against using triggers to automatically execute commands and just wait patiently for your character to complete the writhe.


I was going through all of my codes for Nexus and adding a do nothing clause (reference: #if $herb 1 {#wait 1000} elsif $wri 1 { } else {#send eat Funyuns}) where $herb 1 is equivalent to herb balance being off, thereby waiting 1 second, then $wri is my writhing variable and if it equaled 1 then nothing would happen.

Then, I thought, why not group my writhing triggers in a separate group as the rest of my curing triggers. That way, when a trigger turning my writhing function on (reference: #set wri 1) it would also execute #groupoff curing. Thereby, stopping any other trigger from registering until the writhed free newline came up which would then trigger #set wri 0 and #groupon curing.

The largest shortcoming of this method is that you won't trigger any new afflictions when the newline comes up. Not that big of a deal while you're restricted, however, it is a major problem afterwards when you have 10 afflictions you have to try to cure before you die in agony. My solution for that is as follows:

If you have a variable for every affliction then when you use DIAGNOSE it would set the value for that affliction to 1, then check for the appropriate balance and execute the action necessary to cure it. However, that gets boggy quick. As we all know, the more reflexes Nexus has to search through the slower it runs (common sense). So, here is a solution to the solution. Set those afflictions in a group unto themselves. During unrestricted combat (combat where you aren't tangled, impaled, et cetera) have that group disabled as well. When you writhe free, code in the command #groupon afflictions before you code in #send diag (which executes DIAGNOSE for those who don't know) in the trigger for "You have writhed free...." newlines.

As a note, I am still working through my own system of coding. It is based around a theory that minimizes the aliases and variables in use. The coding is a bit extensive, but as soon as I get it all done I will be glad to share it here and gather some hints. As it is now, it works on individual afflictions that I test out, but we'll see how it works in actual combat. Anyhow, I hope that the above has proven helpful, at least in helping to develop the theories of those who are smarter than me. Take care!
Shiri2008-06-13 13:54:19
The other problem with #grouping on and off is that it sometimes deletes everything in that group for no readily apparent reason.