Thoughts on queuing and elixirs

[Ageranu]

On queueing, I think the best way to follow it would be to complete it as a alias (if x and y) {action;set action_var 1}, with triggers doing <trigger> if (action_var) {alias}.

example: bash (if bal and equib) {kick foo;set bashing_var 1}, <You have recovered balance.> (if bashing_var 1) {bash}

not sure if this is too clunky for normal use though.  Other than that I like the basher 2, as this will turn off bashing if for example you get uder attack, or are stopped do to affliction etc.  Comments?

And on elixlist: I think the running of a pour script to manage the elxiirs would be really hard to manage, and possibly create unnessary spam, perhaps something more like a drop 50 mass, ih, get 50 mass ((note number picked up)) (use one ### picked from IH for all mass applications), then when "you use the last of the vial" subtract from a VAR listing number picked up, and then you have a early warning system, rather than a large spam attack every time you log in.  Plus you also need to know how many sips, some people fill better than others :P

don't know if this helps, but I want to try and throw ideas in, even if they are stupid.

[shograt]

Well, the first concept already exists - in my syntax (enter this into a 'new tiddly' on the sandbox):

|!alias|!message|!requirements|!action|
|bash||bal(yes) eq(yes)|do(kick TARGET) bashing(yes)|
|     |bal(yes) bashing(yes) q(6)|goto(bash)|
... Unless you meant actually changing the syntax, from table-based to more of a lnaguage-type syntax?

Elixlist will still take some thought. I'll try to use the current methods to code one, and see how it turns out.