Shenanigunner

Annnnd... I lived with my pretty little Rest macro for two days before realizing it worked better, was easier to manage and paired with a cancel bind better as a bind. But macro away, folks, macro away... :)

It works fine in a bind. I can use /bind Shift+Q "powexec_location target quicksand" Yep. See the Guide for complete details on how to use all the command's targeting options.

Awright, awright, pal - Arena. Now. Macros vs Binds: the Final Showdown. :D The truly great thing about this insanely multilayered game is that 'whatever works, works.'

Adding custom windows is a pretty advanced technique, up there with editing PIGG files and the like. I use some of those techniques myself, but I'd hesitate at recommending them to novice and average players. I'm not at all down on macros - I just think they are used as a general solution in many cases where a bind would be far more effective. The GABB bindset doesn't change most of the main gameplay keys. It just clears out all the bizarre old comma, semicolon, Alt-F-this stuff and sorts the functions into sensible intuitive order. Removing a lot of keys that if accidentally hit will screw up a battle is part of it. Putting a full array of chat responses on intuitive keys is another. But I fully understand staying with something living in your digital memory. :)

It may be easier, overall, to just assign your costume slots to the NumPad if you don't use it for anything else. Put your main combat look on NumPad0, so it's easy to hit, and your street look on NumPad1... then any others on the rest. I use (numpad) Multiply, myself - bare, it switches to Slot 1, my combat armor; Ctrl+Multiply switches to street look. Shift and Alt could be used for other looks. I'm not sure combining the change with, say, armor activation is all that great an idea, appealing as it is.

The key to using binds effectively is to start with a sensible keymap - like, ahem, the GABB layout - and then use a similarly sensible, consistent keymap for all added functions. I run a tank, sentinel, blaster, stalker, corruptor and mastermind and have found ways to make intuitive mappings for all of them. A cheat sheet helps if I haven't played the alt for a while, but even on first return and using old, old bindfiles I could make reasonable guesses about how I'd mapped the powers. Trying to use random associations around the original keymap and having them be different across alts is... not necessary. :) And the /macro_image command, while needing a little work and experimentation to find good power icons that don't blend into your standard powerset, is a big help for macronauts. It is, by the way, amply documented in the Guide. No need to chase discussion links. The Guide is in my sig. I should have repeated the link in the text for clarity.

Well, there are nine trays you can stack macros in. That's not too big a limitation. The game having solid built-in support for bind management is a huge plus, IMHO. Manually writting, saving and loading macros from offline sources is... good, but not nearly as seamless. They're also dependent on search-and-activate, which is an unnecessary hurdle in combat situations. I know I'm a lot faster with a key combo than finding, pointing and clicking a little screen dot when the fur's flying. As for remembering binds, anything that starts with the original key mapping is going to be a disaster. That's why I rewrote mine over years and now offer the polished, modern-era, intuitive GABB model as a much better starting point. It even comes with a cheat-sheet. :)

I have always preferred keybinds to macros, but in yacking with players and the community I found that there's a faction that sees macros as the way to manage special commands, while leaving the key mapping largely the same. So today I wrote a cute lil' macro to combine Rest with a team message (so the wankers don't run off to the next battle while their big gun is catching up). Works great. But then I realized the big difference between the two, and the big, big drawback of macros: you can't save them. You can't easily transfer them to other alts or players. If you accidentally delete one (which, of course, I have never ever done), it's gone forever. Binds have a whole set of management tools built in. (OTOH, macros are a tad easier to edit on the fly.) Macros have their place, especially in rolling-tray command sets. But they're written on the wind, as it were...

Running a squishie for pretty much the first time since return, I discover the frequent need to Rest. I also discover that teammates don't notice their big gun is not available for the next battle. My practice is to keep Rest in slot 10 of tray 1, so that a quick 0-key activates and releases it. I've moved the actual Rest icon to tray 2, slot 10, and put this macro in its place: /macro_image DayJob_SingleTargetHeal REST "powexectoggleon Rest$$g ***RESTING!***" This toggles Rest on and sends the team-channel message that you need to hold up, guys. If necessary, you can click or 0-key it again to send the message again, without interrupting Rest. Since you usually have the luxury of time to come out of Rest, clicking the Rest icon above it works fine. You could also write a quick un-Rest bind or macro. Adding a whistle emote or other noisemaker might help teammates notice your absence. This uses, BTW, the cool macro_image command that summons any power icon from the game set. I've selected the nice gold Heal icon by default; you can find others in the complete list on the Guide website.

Quotes are only optional on binds and macros if you accept the occasional mis-parse. They do help, IME. There isn't really any need to double-call the power. If the _location placement fails, it leaves you with a targeting circle anyway. (The most common failure is trying to place outside a power's range - the notable one being Recall Friend, which has only about a 24-foot incoming range.) It's a very well-implemented command that by all preceding development limitations shouldn't work at all. :)

The magic bullet you're looking for is the /powexec_location command. Full docs in the Guide. Basically, this power replaces the need for a mouse-click with a targeting command. For your purpose, try this: /bind P "powexec_location target Lightning Rod" ...and that should cast the power right on whichever foe you have targeted. You could add a target_near command to make it a one-stop target-and-attack, too. I use a variation to call Voltaic Sentinel: /bind U "powexec_location 0:50 Voltaic Sentinel" ...which casts it 50 feet right in front of me (0 degrees). This command works with any point-and-click power and opens up a whole barrel of bind/macro possiblities.

I don't think so. They're just wired to the macro, which has no recharge time. Any powers triggered would have an active icon; I guess you could stack them in trays for recharge monitoring.

Wikis are when many people participate to build and update the info. From what I've seen, Paragon Wiki has barely been touched since the return and update of the game. And the practice of bookmarking and linking to discussion posts is just too awkward to take seriously. So, sorry if as a writer I put it all in a concise, fully-updated, instantly-accessible and searchable book. :D

Any serious macro-users who would like to use power-tray icons instead of 2- and 3-letter gray ones, the /macro_image command has been sorted out and documented. See the updated Guide and the accompanying long, long, long list of power icon names at www.dgath.com/coh!

Anyone using Dual Pistols and the Swap Ammo powers... here's a bind set that will make swaps fast and easy on a standard keyboard. Not recommended for compact/laptop layouts. /bind SYSRQ "powexecname Cryo Ammunition" /bind SCROLL "powexecname Incendiary Ammunition" /bind PAUSE "powexecname Chemical Ammunition" /bind INSERT "powexectoggleoff Cryo Ammunition$$powexectoggleoff Incendiary Ammunition$$powexectoggleoff Chemical Ammunition" Puts three essentially useless keys to good order and remaps one not-very-useful key as well. The only glitch is that you might exit the game with Scroll Lock activated; a tap fixes that and there aren't ten programs in the world that actually read that setting. Note that there is sometimes a bug in which the key will only bind using 'SYSREQ' even though the bindfile saves it as 'SYSRQ.' Reports back on this would be useful.

That's the old-school bind. (Insert very smug face for having just discovered this new trick.) /bind LeftDoubleClick "powexec_name Teleport" - or Translocate. That's the way (uh huh, uh huh) you dooooo it... now. :)

Yep, rollover binds and macros can get around a lot of limitations, but it's still one-keypress-per-power with very few exceptions. You can't make a newly loaded bind line or macro self-execute.

Has anyone gotten a PS4/DS4 controller to work well with CoX, using DS4Windows or an equivalent? Between the game's controller/joystick button mapping and DS4W's configuration, I have a pretty good setup working, but absolutely nothing on either side will recognize motion of the right joystick. Anyone?

Underscores are ignored by the command processor; you can use them or not, as they help you parse someofthelongercommandnames. There isn't even a standard 'spelling' with them: powexectoggleon, pow_exec_toggle_on and powexec_toggle_on are all equivalent. Underscores are stripped out; the letters remaining have to be correct, though. Not sure if a double underscore will be ignored. Have to test. ETA: Yup, scads of underscores, even in series, are just ignored. OP, I suspect you're mistyping your bind commands. All those you list should work. I refer you to the Technical Guide for comprehensive, updated information: http://www.dgath.com/coh/

That's for ranged powers. Melee types should use the Grapple bind - /bind G "targetenemynear$$follow" ...

I'm not sure the toggle-on limitation was universal, and I know it was initiated/expanded fairly late in the game. I have bind files from my last alts that had two- and three-power "on" binds that I know worked as intended. They have not worked since relaunch, and you're correct in saying that one press per power is needed for full activation. As long as you use the -on and -off commands on separate keys, it's only a little more complicated than one-press binds.

Good bindset. I use NUMPAD0 for my preferred pose and 1-3 for the others, since the numpad doesn't have much use otherwise for my flying alts. The combined commands don't work together too smoothly, so I use: /bind Y "powexecname Fly" - general fly/fall toggle. /bind W "+forward$$emote flypose1" - pretty reliable about toggling on the pose, and is just null for running. /bind R "++autorun$$emote flypose1" - pretty reliable about the pose for long flights. What works better but takes a little retraining is: /bind R "autorun 1$$emote flypose1" - tap twice if needed, no toggling. /bind SPACE "+up$$autorun 0" - up key, cancel autorun And for one-handed jump/fly-over: /bind MOUSECHORD "+up" - both keys elevate the situation while you do something else with the other hand.

That command should work, with some tweaking if needed. The idea of letting the power determine its own firing point at maximum range is a great one for most damage alts, especially blasters. However, you have to have a hair trigger on the run-away key (S, usually) to keep your alt from running up to give that boss a hug right after firing an attack. :)

I've added a new resource to the website - not-a-guide, not-a-wiki, not-a-FAQ list of the little stuff every player needs to know and only learns by stumbling around for a few levels, or asking the same old questions in Help. Yes, there are a zillion references out there, but Paragon Wiki is massive and largely outdated, and referring people to post 26 of Reddit topics is random and clumsy. Hence Gunner's Stuff No One Thought to Tell You List, or GSNOTTY. Pass it on to the noobs of your acquaintance.

So I finally founded my own SG for my alts and all the stubborn solo types who just need base assets... and of course disappeared into the base editor for what seemed like two years. :) Fun. Making it free: even more fun. ;D But being the bind and command guy, I had to mess with the /editbase command. Here's some notes; takeaways and comments welcome. /editbase only works while in the base. It can be used anywhere, not just in the Entrance Room. Quick shortcut when you want to modify your furthest-away room. /editbase 1 enters base-editing mode from anywhere, but repositions your alt in the Entrance Room. A minor shortcut for those who don't want to jog back to the start to go into edit mode. /editbase 2 goes into isometric plot-view mode... but without editing privileges. /editbase 3 goes into plan plot-view mode... but without editing privileges. Higher numbers respond just like 3. Not sure what to make of these "features." Maybe 2 and 3 are more useful when starting with an empty plot and allow you to base-build from plot definition; I didn't want to mess up my pretty new layout by trying. One warning, though: selecting base editing with one or more of these commands seems to have reset my keybinds, or switched them to a base-editing model. (I rebind DEL to clear-chat, for example, and it's used in base editing to, well, delete things.) I'd recommend doing a /bindsavefile before messing with these commands. Next stop: analyzing and optimizing a base-edit bind set. Comments welcome.