Best Of

So first things first, go into your Nexus settings and disable the "Do not show any prompt lines at all" option, then CONFIG PROMPT ALL to make sure your prompt isn't only giving you HME, power, and eq+balance. All should make your prompt look like this:

00000h, 00000m, 00000e, 10p BeisSlrx-

or

00000h, 00000m, 00000e, 10p BeiSslrx-

I can't recall which is first, but the B is beast balance (whether you can BEAST ORDER or not), e is equilibrium, lr is arm balance (left and right) (you may need to do CONFIG ARMBALANCE ON to see these), and x is general balance as usual. The new ones for you are probably i, S, and s. These are your id, Superstratus, and substratus channel balances respectively.

Your Psionics+Psymet defenses that don't lock channels are MindBar, Secondsight, Ironskin, Regeneration, Enhancement, Energycontainment, Gliding, Psisense, and BodyDensity. Raise these first as needed, most of them are fire and forget with no reason not to use them (see their individual AB files for what channels they can be raised on and extra syntaxes), but with the rooting changes proposed you may or may not want BodyDensity.

Anything with an * is a little trickier, because those will lock the channel you raise them to, for instance PsiArmour can be raised on any of the three channels and should likely be one you have up any time you aren't already capped on cutting and blunt resist up to 8 weight, but if you PSI ID PSIARMOUR to put it on the id channel, you can no longer use any abilities on the id channel without unlocking and losing PsiArmour first.

With psionics, you can use any channel that has its balance as long as you have equilibrium, but aside from psi channels you are not considered to have equilibrium until you either fully lock or regain that channel.

This means that, in essence, you can stack psionic commands to the same command line and expect all three actions to go through, for instance if you SM ADD PSI ID MINDBAR||PSI SUB SECONDSIGHT||PSI SUPER IRONSKIN, then when that stratagem fires it will consume all three channels and raise all three defenses, letting you recover them all at the same time. This will still count as being off-equilibrium until you do get all three back (think in this case Superstratus will come back last).

So, to recap:

- Force Nexus to give you a prompt

- CONFIG PROMPT ALL

- i = id channel
- S = Superstratus

- s = substratus

- Psi channels are independent and can be consumed at the same time

- You are considered off-equilibrium if any channel is recovering except for using other unlocked psi channels
- Abilities with an * in the AB PSIONICS or AB PSYCHOMETABOLISM will lock a channel and prevent it from being used for anything else

- You can 'stack' psi commands to use more than one at the same time as long as the channel you're using is open and the ability can use it.

- Don't be afraid to experiment with your channels to find what's best for a given situation. (PK, PvE, Aetherhunting, Influencing, or questing might have different channel setups)

As a general set of recommendations, Psiarmour should be a go-to unless you're overcapped on the resistances it gives, or you're not going to be hunting or in PvP at all. Pheremones will shut down anyone that relies on an enemy list (mages, druids, guardians' and wiccans' entities, etc). If you're going aetherhunting, especially as an active siphoner or empath, Lock Ironwill. Shaddus already mentioned Introspection, which is nice on its own but also has a couple of synergies as well.

This is a double-post but the second bit of input I have is independent of the questions you asked:

When you're pricing out things, don't forget crucibles. For instance, if Hallifax has the lowest prices on everything (believe me, it does not, but this is a hypothetical), and they're selling Milk at 30gp/ea, but Vegetables at 10gp/ea, then the price for milk is 20gp/ea for every 50 crucible output I'm willing to devote to milk.

The groups are: {iron, gold, silver, platinum, mercury}; {grain, milk, fruit, vegetables, sugar}; {leather, cloth, rope, silk, salt}; {poultry, fish, meat, eggs, sulfur}

It's likely going to pretty consistently be that the first group are priced as-is unless mercury gets stupid cheap or stupid expensive for you, the second group is going to have either grain or veg as the price point, the third will probably be leather or cloth, and the last is probably eggs, poultry, or meat. For most recipes this might not matter, but anything that needs salt, sulfur, or sugar is going to be wildly different.

1) Yes. Split this into two triggers. Have this one shove the output text into a string variable called something like price (might need to explicitly make it global, I'm not sure with Nexus) and set another variable to true (I'd probably make it pricer, priceCheck, or something in that milieu.)

For the second, either trigger the prompt or "Comments:" or see if there's already a trigger for when you receive the prompt (the influencer script might have one, as an example) and add an if statement to check whether your boolean is true, and if it is, have it display your price string with an optional but recommended newline leading character and set the boolean false.

In lua, this would look something like

3) This is going to be a pain one way or another. Your 'best' bet is to have something set up so that you enter a command to start the thing, gag everything for a while, then take each recipe/pattern number it gets, save the original output line, check the recipe, and either save the price value to a table in much the same way that you had it handle the price per commodity, then spit out a modified list with the original output + price or have it handle each line as it gets there by spitting the original line + price out when it gets there, then turn off the trigger group that does the price checking when you hit "Total:".  The reason you might want to do it the first way is that it would let you run that hot mess once and deal with the processing of both triggers together across as many recipes as you're getting, but then allow you to set up a second set of much less intense triggers that just remembers the original numbers and a string that's the regular output + price.

ie it goes through the whole list once, gagging the >100 lines that RECIPES GOURMET will give you plus the however many lines you'd get by inspecting each recipe and shoving the output lines into a table with the recipe number as a key and the line itself with the price added as a second field. Then if you do RECIPES GOURMET again it'll see if the recipe number is in its table, and if so it'll replace the line with the new output with price without having to re-scrape the recipe.