/inspexecname

I have a pair of binds, one which has /inspexecname commands for most small inspirations, and one that has the commands for most of the mediums. When I get into a tough fight, I mash one or both to automatically eat a huge pile of insps. Problem is that it seems that "Rage" and "Insight" appear in the names of multiple inspirations, and I often find myself eating inspirations I hadn't meant to.

It there a way to make it so that "Rage" and "Insight" only refer to the small inspirations, and not any that have that string in their name?

IIRC, use the full name of the inspiration, replacing spaces with underscores. For example, use Insight, Keen_Insight and Uncanny_Insight to differentiate between small, medium and large.

Not sure if this is what you mean. My Yellow bind looks like:

inspexecname "insight"$$inspexecname "keen_insight"$$inspexecname "uncanny_insight"

So when I hit that bind it executes a small yellow. If there is no small yellow it eats a medium, and if there are no mediums available it uses a large.

I don't know of any way you can make pressing a button eat ONLY an "Insight" and never touch a "Keen Insight" or "Uncanny Insight"

Without pulling it up, my bind is some variation on

inspexecname insight$$inspexecname rage$$inspexecname luck$$inspexec sturdy$$inspexecname respite$$inspexecname catch a breath

When I need a boost, or want to clear my tray for better inspirations, I just mash the button until it stops using insps. After doing this, I often find that my buff bar includes 2 or 3 stacks of red and yellow insps - one for each size it used.

Here's the really weird thing: When I used the bind just a short while ago, I watched a Resurgence disappear from my tray. And it's not possible that I bumped a different key and used it; I have NO binds that use T3 insps, nor binds that execute an inspiration slot (I unmapped them all). It should be impossible for me to use a T3 insp of any sort, save the oddity with "overlapping" names. I have NO idea how it's using T3s that aren't named - in full or in part - in my binds.

You might want to actually take a look at your binds, either by dumping the entire thing into a file with /BindSave or using the /ShowBind key, because /InspExecName doesn't work the way you think it does. It requires the full complete name, the same way that the power slash commands require the full name of the power.

I just double checked my making a bind using insight (/bind Numpad0 inspexecname Insight) and bought some Insights and some Keen Insights. The bind use the Insights and didn't use the Keen Insights no matter how many times I pressed it. Next, I change it to Rage (/bind Numpad0 inspexecname Rage) and bought some Enrages and some Focused Rages. Using just rage in the name would not use any of these inspirations.

Your binds are not what you think they are.

If what StarGeek says is true (/inspexecname requires the full name) -- and I have to believe it is -- then the problem is likely what Roderick pointed out. Maybe there is a bug where T2 or T3 insps get used when the T1 insps are called?

Very interesting. Something odd is happening with you, since I just used your bind, and had completely different results. Only the named inspirations were used, nothing else.

Not positive but here is what I think may be happening...

It has to do with the button mashing really fast. Basically you are hitting a bunch of times in a row before the game can actually start processing the command fully. So you make it try to eat a Catch of Breath twice in rapid succession, it works the first time and pull the inspiration from the tray where it was. Well you hit it so fast for that second time that the game still thinks there is a Catch of Breath in that same tray position and uses the inspiration that is there, no matter what it is.

If you wanna test, buy a few of the small inspirations at the very top row of your tray, and all the medium and large at the bottom rows of the tray. Do your bind button mashing and see which is being used.

Side note as said before, I believe that the bind for Insight should not work for Keen Insight without something weird going on...

MrTogo has an interesting idea. I'll experiment more later, adn see if I can find a pattern to what's happening so I can submit a proper bug report.

Yeah, MrTogo has the right of it. I've long since compensated for this behavior and had forgotten about it.