Shenanigunner

I think you completely fail to grasp the point of "forums," "feedback" and "useful." I think all toons should be turned into 8-foot pink bunnies with the Candy Cane power set... let's have that mass cheer! You have to grasp the difference between "Chee, woudn't this be nice" and "I think the game sucks unless [this change] is implemented... who's with me?" You apparently don't; every one of your ideas should send the devs into burning midnight oil to achieve. You seem to have a similarly weak grasp of JUST HOW MUCH EFFING WORK many of these changes involve... from unpaid developers. You might want to think about that as WHY your suggestions get poor responses... they are often both niche/unreasonable AND involve major code surgery. No, you're not going to get a lot of cheering. If you can't deal with negative (and almost always quite civil) responses... well, maybe you're in the wrong forums. I gave you the solution you are looking for; it just isn't implemented in the way you are demanding. I tap U three times and all three Leadership toggles are up, about as fast as I could click one /alltogglesup macro. Too slow? Use the auto-fire bind set and you'll never have a toggle down nor need to click one again, along with all your click-fire powers. Happy to hear why that's not good enough, given that you could have it implemented in fifteen minutes, it involves no Dev time already loaded with much more critical issues, and doesn't have the chance of breaking or destabilizing the game.

I don't think I was; I resent being attacked for not mindlessly cheering an idea. Since there is a workaround that's 99% of this change, I can't give it a thumbs-up just to suit a minority of players who build toggle-heavy alts and then don't like it. I have a pretty strong idea that it's NOT a trivial task and COULD break the whole command structure as SwitchFade suggests, pushing it even further down the list of things the Devs should spend time on. I find the one-bind and auto-bind methods to work just fine on my toggle-driven alts. An all-up command... just feels like an exploit to me.

If you can't read, why do you post? It is trivial to write a macro or bind to bring up all toggles in a matter of seconds. I'd say that's a pretty productive, useful comment. But here, have another: It's almost as trivial to write a bind set that makes toggles and click powers essentially perma. You're welcome. Sorry some of us more experienced players and community members think the devs have better things to do than completely reconfigure the command processing structure because you are impatient or think it would be kewl or somehow think powers are too weak and slow in this game.

No, the party to avoid making the game more auto for cream puff players has spoken.

It's trivial to write a bind or macro that will bring up multiple toggles with multiple taps.

Clearly, no one recalls.

Blue light is either pseudoscientific nonsense (or at least greatly exaggerated)... or a leftover bit of Heinlein.

Almost certainly not. The command parsing system was carefully built to prevent almost all forms of stacking, scripting, and automation. However, you can simulate autofire and auto toggle with a set of rolling binds. There's two posts over in general, and I just added the material to the Guide. Just a bit involved to set up, but it works very very well.

There are, quite simply, very few things that have given me more joy, while simultaneously relieving that old heartache of loss, than the return of this game.

Step 1: drag the legs slider to minimum. Step 2: set a reasonable height. Step 3: adjust head size (usually somewhat smaller). I know it's a cartoon world, but giraffe-leg toons with big heads (and breasts like moons) gets exasperating.

Weak workaround for getting two powers into one bind/macro. Simply using ...name or ...toggleon works, just requires one tap per power. I wouldn't try to put long-term click powers in a multiple macro for several reasons. But whoom... can't disagree! And yes, ...toggleon and ...toggleoff are literally game changers for those fussy powers and foolproof binds.

That's it. Using blanks took out all the bugs, and I suspect not using ...auto helps, too. Great info, thanks. So [1] use a blank file in between each power-activating one, and [2] ditch powexecauto for just powexecname. There really isn;'t any reason to drag the auto quirks into this kind of a setup, other than the very minor advantage of leaving one (1) power autofiring. ETA: activation times still hold things up, if you tap W while Rage or whatever is firing. No worries, it just hits on the next pass. Gad, this fixes SO many alt/gameplay issues! May its functionality remain unbroken. 🙂 I added a bonus: bind powexectoggleoffs for all these powers to some useful key (I use CTRL+U), along with a powexec_abort to undo any leftover auto-fire. That lets you kill all the auras, buffs, flames, lightning, and movement stuff in one whack, which is often convenient.

Hmm. Good point. I use empty files for my rolling chat binds but only to space them out (so every activation doesn't trigger a chat quote). I don't think I've ever had rolling binds activate on key release. Must experiment... What I'm seeing is more "skips" in the sequence, where Keypress 1 activates power A, but Keypress 2 does nothing, then Keypress 3 activates power B. I think that's due to activation times but haven't nailed it down. I also see a weird bug when using multiple auto-fire powers. I use the W bind to fire Rage, then to fire Hasten... and the green ring skips back to Rage. Every time. I don't think the command parser really likes multiple powers on autofire; it might be more effective just to call the click powers with ...name. Autofire becomes moot in this scenario.

This is a great post, worthy of tidying up into a guide. I added a section on this technique to my Guide, simplifying the explanation and examples for both types of movement bind (auto-fire and toggle-up), based on another discussion and some past work on the idea. (I haven't written anything on the farming-support idea of Insp combining, though.) A couple of points: While writing the rolling bind files can be a little tedious, it does work fine, with (as far as I can tell) zero impact on movement, gameplay or activation delays. The idea of putting different powers on different keys really isn't necessary, and does limit the options. The rolling-bind option can manage... a dozen or more powers if needed. As long as you remember that it's forward-march that keeps these powers up, it's not hard to give W extra taps, even when you're just standing around. You can run through a cycle of 5 or more binds in a few seconds without moving more than a few feet. The firing order of powers using this can be erratic, for no reason I have been able to pin down. It's rarely a simple matter of them firing in the order the files roll over. (I think it's mostly activation times and too-quick taps of the W key, but not entirely.) So trying to set this up with a precise 'firing order' is probably fruitless. (And not necessary, as far as I can think the idea through.) Keep in mind that this did not work for some good stretch of the game revisions. I remember trying it fairly early, then trying it with the collaboration of another bind guy, and not being able to make autofire powers work in any overlapping fashion. So... this technique could go back in the dustbin with changes (deliberate or coincidental) in the command parsing process. And we'll regroup and move on. 😄 ETA: if you find writing and editing bindfiles a chore, I have one and a half words for you: Notepad++. Free, great, manages multiple files like a champ, keeps your whole file set open for quick open-edit-save-close-load operations. Takes only seconds to load and use even while the game is waiting.

I didn't know her. But it pleases me that she knew us. This community is not to be undervalued.

And gosharoonie, it does. Section added to the Guide (2.9). Thanks, Placta!

Okay, that approach. Nifty implementation! 👍 It works, but I've seen problems. For one thing, I'm surprised you don't see latching of the +forward command; that damned parsing bug does not like combining + commands with any others and often reads them as ++ (latch on or toggle). Also, at various times I've experimented with it, powers would not accept an auto assignment and/or fire until the last auto power had expired. I'll have to go tinker with the current situation.

Curious as to how you structure these. Isn't a "rotating bind" just a click of the powers? How does assigning autofire change the process? Also, I tend to run at lower levels, but I've all but stopped taking Hasten. It can't be made perma any more with SOs; not sure how many IOs and sets it takes to get there. Besides taking the other SS pool (Experimentation?), I can usually find a better power choice. When I do have it, I don't use autofire, preferring to hit it just before a big scrap.

If a bind is mapped to +zoomin or several other view controls, it can "latch" on and not be easily overridden. Another example of the '+COMMAND' parsing bug.

This, in spades. I used to wish mightily that the GMs would maybe lift the fog one day a year so we could see the whole zone... and now I'd much prefer to have the fog and the vanishing civs back. It's just another zone now.

You'd think that smashing their toes would slow them down, yes. 😛

My stalker and blaster both take a long animation to fire the snipe from an un-aggroed position or in hide/invis, but fire it almost instantly in combat (with greatly reduced damage). I think that's how they are supposed to work after the fix from always having a long animation/interrupt.

+1 (at least) on this. Combining team-affect powers with a chat string can really help team coordination and effectiveness. I use it for Rest on all my alts: /bind 0 "powexectoggleon Rest$$g <color white><bgcolor #4466ff><scale 4><bordercolor blue>^^^ Takin' a break! ^^^" /bind - "powexectoggleoff Rest$$g <color #4466ff><bgcolor white><scale 4><bordercolor blue>— Okay, let's go! —" ...and tweak the text and colors to suit the alt's theme. It's VERY helpful to let mates know you're recharging, and when you're done. (I keep Rest in Slot 0 for consistency, and the editable text is everything following the last >.) But ditto on things like buffs and major attack powers. Rolling binds (with the occasional silence on frequently-used powers) can make it more tolerable.

For me, it's a matter of putting "urgent" commands on consistent, accessible keys, while still using 1-0 for most attack and debuff powers. It's a balance between default/tray keys, custom binds and macros, with the goal to make the (frankly clumsy) control system as easy and transparent as possible. If you haven't looked through the GABB binds for ones to pilfer, you might find it useful, even if the complete remapping isn't to your taste. That and the custom binds in the Guide and on the site. Hey, a quarter second is a quarter second in battle. 🙂

Yes, camdist goes to 120, wheel zoom only to 80. But any touch of the wheel and it will snap to 80.