Master-Blade

I like your cute little phrases like this, but I wasn't necessarily saying it was minor, just that it isn't as huge a problem as it used to be now that we don't have the graphic at our feet anymore.

I do agree with you.. sitting in market or just hanging out is mostly pointless to be running a toggle, especially one that affects others. Even if most machines can handle it just fine, we should consider the people who are on systems that can't. And some people worked hard on their costumes and want people to see it. They don't want to be invisible if they don't have to be.

IIRC, the graphic for shadow fall is not "contageous" anymore. Only the person with the toggle on will show the graphic. Other people are still granted the benefits and slight translucency, but they wont have the colored shroud that many people think is annoying.

You can certainly use the refer-a-friend to add a new game account to your own Master account. I've done it a couple of times. You can also use the invite-a-friend-back system to reactivate one of your expired accounts (if it's been inactive for more than 90 days).

That's not exactly true. What would happen if you had a third command in there as well? There is no way for it to just pick out the commands it wants to run. The + makes the whole command line run twice. Once when the key is pressed, and again when the key is released.

In this case, it may appear like it's only running the teamselect on keypress because the powexec is run simultaneously. Depending on any number of factors, your target may not register on your client at the time the power execution is run, which is why you would have had to run it a second time. Additionally, now that your target is already set from the first run of the command, you wouldn't notice that the teamselect is actually being run again anyway.

It's more noticeable what's going on if you used the "next teammate" bind instead of designating an actual number, but that's part of why I don't like to do it that way. An easier test is simply to string together a whole bunch of text commands and then put the +$$ in front of it. Pressing the key will display all the text twice.

This is also how the SpeedOnDemand binds work.

Example:
/bind W "+forward$$powexecname super speed"

On keypress, the W will make you move forward and activate super speed. On key release, you will stop moving forward and disable super speed. It runs the full command twice, not just part of it.

For some reason, I think it used to be 15 minutes, but now it's 30 minutes, which is almost the standard length of a raid as well. If you are the first one to plant your bomb, it's likely the shield will go back up shortly after you are allowed to click your second bomb.

Back when the requirement was 25 bombs, that could be useful, but not really anymore. Since you have to defeat the boss 10 times for a badge, you'll have to participate in at least 10 raids anyway, so why not just get your 1 bomb each time to make the new requirement of only 10? There isn't any benefit to getting 2.

That also works for objectives in missions. Even if you are dead, you can still click things. It can make those repetitive "click 4 at once" missions in DrQ much quicker. Instead of clearing the room to free up the clickie, just suicide on top of it, then click when prompted by the team.

Sidenote tip#2: If you die in the Shadow Shard, you'll return directly to the spot you died if you "Go to Base" and click on your blue portal. If you are in a mission, you'll return to the mission door. This works on any other zone that doesn't have a beacon as well, including the Sewers, Abandoned Sewers, The Tunnels in the Hollows, PvP and Hami zones.

*runs off a cliff (make sure you bring your parachute). haha

Yep, the ones we listed have the teamselect and the power execution on a single command. It's quite convenient. Just make sure that when you copy/paste them, you typed /bind first. lol

Alternately, you can simply copy/paste that into a text file named c:\binds\sb.txt, then quickly load it onto your character by typing:
/bindloadfile c:\binds\sb.txt

Yes, you program all those binds, and then it's as simple as pressing the button for teammate, then pressing the power. Or, as I and Kitsune have set up, the single key will select the player and automatically SB them (if they are in range and LoS).

*fixed

You shouldn't have to double-tap those. The act of pressing the key and the act of releasing the key with both run the command, reducing the need to hit it a second time.

But Agg was probably referring to her own post that had the same binds... right down to the ADD key.

Thanks. I've edited a few things on the wiki in the past, but I don't like messing with things that have a format. I bet it's easy, but I just feel like I'll mess it up. Not that I couldn't just easily figure it out and fix it.. but you know. lol

Thanks again. It looks great! That should clear up some confusion.

Yeah true. We can't always count on everything working the same way. For all we know, some odd driver might add support for an extra modifier key. I dunno.

Nice. I'd probably fix/clarify the L and R modifiers as well, but I'm always afraid I'm going to mess up the format of the tables when I edit stuff like that. lol

That makes me kinda want to test it out, just to clear up the wiki. I've seen it listed for a long time as a keyname, so I did nothing but assume it would actually work for FN+X as an example. That combination has no other uses.

What you say makes a lot of sense though, and it would certainly prevent the mess of what happens if you bound and pressed FN+M. Would it actually send FN+M, or send Numpad0?

Edit:
Even though I'm not playing on a laptop, I just typed "/bind FN+M L hi", and checked the bindfile to see that FN+M does not exist. The FN was ignored and it simply bound it to M alone, and pressing M activates the bind. haha

Well that answers that.

Yep, slip of the finger and corrected. The [uirl] tag doesn't exist. haha
Thanks.

But Agg is still not wrong. The mousechord involves buttons, not keys. haha j.k
I love the mousechord.

According to the wiki, the FN key on laptops can also be used as another modifier. I've never tried it though, so I don't know how well that works when you consider the overlapping numpad on laptop keyboards. That could get messy.

Anyway, looking at the wiki, it seems that chord section does need a little bit of an edit for clarification about the way L and R keys work. Those should be listed under the Key Names section instead, and note that the L and R are ignored when used as a chord.

And.. worst case scenario, just get yourself to the bomb, and even if you die, you can still activate it by clicking on Interact on your Target>Action menu, even while dead.

This part is wrong. You cannot specify L or R in a chord. Lshift and Rshift are used only if binding that specific key on it's own. If you want to bind Lshift to activate a power, you can, but you can't specifically designate Lshift+1 as a bind, and you cannot bind Lshift+1 and Rshift+1 to do different things. If you attempt it, it will default the command to shift+1 anyway, and pressing rshift+1 will end up overwriting your lshift+1 bind, and pressing lshift+1 will do the same action as you tried to bind only Rshift+1 to do.

You can further prove this by creating a Lshift+1 bind, and then doing a /bindsavefile. You don't see lshift+1 in the file, but shift+1 will be there instead.

To simplify/clarify: You can use Lshift+1 when creating the bind if you want to, but the L wont actually do anything for you.