Masterminds have known for some time that there is a VERY ODD command parsing discrepancy between commands for Pets that are typed into the chat window, versus those which are stored in a macro or a keybind (including /bindloadfile keybinds). The most obvious one, which runs "hot and cold" depending on patches to the game is the
The former of these two, typed in manually will "work" but the latter will not when done as a macro or a keybind. And to be honest, I've never been able to figure out why these things would parse differently whether they're typed into the chat window or produced by a macro/keybind.
Well ... now I've found another one of these "weird discrepancy" behaviors with the /releasepets command.
If I have a Ninja (Jounin) Pet named "Yon" and I manually type in
Code:
/petcomname Yon releasepets
or even
Code:
/petcomname Yon dismiss
then only the 1 Pet named "Yon" will dismiss.
But, if I'm using a keybind (from a /bindloadfile) that is
Code:
shift+decimal "petcomname Yon releasepets"
or even
Code:
shift+decimal "petcomname Yon dismiss"
and I use the key combo of Shift + Decimal (on the numpad), then not only "Yon" will be dismissed, but ALL OF MY PETS dismiss ... not just the one that I am directly (attempting) to address to be dismissed.
Note that the exact same formulation for Pet Controls so as to issue commands like Attack/Stay/Defend/Aggressive/Passive/Defensive/Goto all work they way they should regardless of whether those commands are issued via typing in the chat window, or via macro or keybind when addressing them to any combination of all Pets or a singular individual Pet. This makes the "indiscriminate" nature of the /releasepets or /dismiss behavior extremely odd, since they only work "globally" for all Pets and will not work in a targeted/individual fashion.
Needless to say, this seems (to me, anyway) to be a *NEW* behavioral discrepancy between how commands are parsed by the game in Issue 21, as prior to this point I could use my /bindloadfile keybinds to issue /releasepets commands to all of my Pets, specific tiers of pets (Genin, Jounin, Oni, in my case) or even individual Pets by name in Issue 20. And the root cause for this discrepancy appears to be how the game processes commands differently depending on whether they come from the chat window (manually typed) from from a macro or keybind (including keybinds from /bindloadfile).
Request investigation/analysis for why this should be so ... that there are any "differences" between manual typing and the use macros/keybinds to issue what would appear to be Identical Commands to the game.
Also, as a side matter for QA to discover the Root Cause ... when my Ninjas receive a /dismiss or a /releasepets command, they will do their Dismissal animation and vanish (as Ninjas are prone to do) ... but their shadows remain on the ground and are easily visible in (halfway) decent lighting conditions during daytime. What is weird about this is that the shadows of the /dismissed Pets continues to replay, over and over and over again, the animation used for the Dismissal. After *several* repeats of the shadows of my Ninjas doing the /dismiss emote, they will all suddenly "pop" out of sight very suddenly.
This tells me, that for Ninja Pets (at least), there were some ... shortcuts ... taken with the Dismissal animation/emote which yield peculiar behaviors when seen using the better graphics now possible in today's game (ie. better shadows). And while this may not be a high priority/"game breaking" bug, since it's more cosmetic than lethal, it could perhaps point towards something ELSE which it might prove wise to tidy up (if the people responsible for this sort of thing ever are given the opportunity to).
It's the end. But the moment has been prepared for ...
Masterminds have known for some time that there is a VERY ODD command parsing discrepancy between commands for Pets that are typed into the chat window, versus those which are stored in a macro or a keybind (including /bindloadfile keybinds). The most obvious one, which runs "hot and cold" depending on patches to the game is the
Well ... now I've found another one of these "weird discrepancy" behaviors with the /releasepets command.
If I have a Ninja (Jounin) Pet named "Yon" and I manually type in
But, if I'm using a keybind (from a /bindloadfile) that is
Note that the exact same formulation for Pet Controls so as to issue commands like Attack/Stay/Defend/Aggressive/Passive/Defensive/Goto all work they way they should regardless of whether those commands are issued via typing in the chat window, or via macro or keybind when addressing them to any combination of all Pets or a singular individual Pet. This makes the "indiscriminate" nature of the /releasepets or /dismiss behavior extremely odd, since they only work "globally" for all Pets and will not work in a targeted/individual fashion.
Needless to say, this seems (to me, anyway) to be a *NEW* behavioral discrepancy between how commands are parsed by the game in Issue 21, as prior to this point I could use my /bindloadfile keybinds to issue /releasepets commands to all of my Pets, specific tiers of pets (Genin, Jounin, Oni, in my case) or even individual Pets by name in Issue 20. And the root cause for this discrepancy appears to be how the game processes commands differently depending on whether they come from the chat window (manually typed) from from a macro or keybind (including keybinds from /bindloadfile).
Request investigation/analysis for why this should be so ... that there are any "differences" between manual typing and the use macros/keybinds to issue what would appear to be Identical Commands to the game.
Also, as a side matter for QA to discover the Root Cause ... when my Ninjas receive a /dismiss or a /releasepets command, they will do their Dismissal animation and vanish (as Ninjas are prone to do) ... but their shadows remain on the ground and are easily visible in (halfway) decent lighting conditions during daytime. What is weird about this is that the shadows of the /dismissed Pets continues to replay, over and over and over again, the animation used for the Dismissal. After *several* repeats of the shadows of my Ninjas doing the /dismiss emote, they will all suddenly "pop" out of sight very suddenly.
This tells me, that for Ninja Pets (at least), there were some ... shortcuts ... taken with the Dismissal animation/emote which yield peculiar behaviors when seen using the better graphics now possible in today's game (ie. better shadows). And while this may not be a high priority/"game breaking" bug, since it's more cosmetic than lethal, it could perhaps point towards something ELSE which it might prove wise to tidy up (if the people responsible for this sort of thing ever are given the opportunity to).