StarGeek

Renowned
  • Posts

    2437
  • Joined

  1. StarGeek

    immortal badge

    I had my characters Rest in front of a CoT Guardian overnight. It took a few weeks to complete.
  2. StarGeek

    CoP Attempt

    Was it just me or did these spawned critters not drop any inspirations at all. I came into it with a near empty tray and I don't believe I ever got a drop from them.
  3. Worse than that, your computer might get infected.

    Important note about City of Heroes wikis.

    Here's the Paragon wiki version of the page you were looking at.
  4. You might want to post in the Mids forums on the Titan network. They're much more likely to see it there.
  5. StarGeek

    Queued

    Moar nerdrage, it sounds just like cowbell!!
  6. StarGeek

    CoP Attempt

    I'm in, if there's room.
  7. StarGeek

    Badge sorting

    I put in notes on where the changes are on that thread.
  8. Your SetTitle list gets off by one at some point after 613 Chrononaut. Speed Demon is 628, not 627. It seems to reset at some point after 1043, the new number for Faultline Finder, as Agent of Order is correct. 1059 comes up as a . (dot) for me instead of 1058, so maybe the reset point is after that.

    Vet Badge Resolute is 1046.

    Everything after Agent of Order appears to be correct.
  9. StarGeek

    Badge sorting

    Quote:
    Originally Posted by Kheldarn View Post
    Another issue, with more badges, and another round of the /settitle numbers getting moved all over the place. I'm not sure if Beef has updated the /settitle numbers yet, but Snow Globe has them listed here.
    And even that list is already out of date. The Vet badge Resolute isn't on there (though a different Resolute is), and I found several that were incorrect (City Traveler, Honorable, Enduring, Genuine, Distinguished, Jubilant, and Exultant).
  10. From that link:

    Will my L50 character be able to visit Praetoria?

    War Witch:
    Yes, but not right off the bat. Right now, we want to give Praetorians as pure an experience as possible and it's hard to give them that if some Paragonian or Rogue Islander shows up, breaking their immersion. So for a little while, we'll keep it Praetorian-only, then as things settle down, we'll open up the link to Primals.
  11. As AquaJaws said, if you've played recently, you've already downloaded it.

    If you still wish to move it, see BillZBubba's Guide for Moving CoH or Installing Test. Personally, I have it on my D: drive.
  12. StarGeek

    Quests

    Quote:
    Originally Posted by Katie V View Post
    There's one exception to the "seven active missions" limit: if you're running a task force, strike force, or trial, …
    AE or Ouroboros mission…

  13. Quote:
    Originally Posted by Memphis_Bill View Post
    2. /getglobalname character, I *believe,* will get the global - if it doesn't have one, wow, that's been inactive for a long, long time.
    Yep. I have someone on my friends list from before globals went in. A /GetGlobalName on her doesn't get a response.
  14. Quote:
    Originally Posted by tanstaafl View Post
    hrrmm I've always enclosed the powexecname in quotes eg /bind R "PowExecName Resurrect".

    Are the quotes as necessary as the doing the _ (eg pow_exec_nam_e)?
    Quotes are not necessary for a single command. When you add the double dollar signs ($$) to separate two commands, then you need to enclose the whole thing in quotes. For example, /bind R "PowExecName Resurrect$$L Get up you lazy bum!" would require quotes. Underscores and capitalization make no difference either way. They can make it easier to read, which is why I usually try and use caps (to avoid my previously mentioned common mistake of using PowerExecName instead of PowExecName). Underscores will extend the size of the bind and some of mine are too close to the maximum length as it is, so I usually don't use them.
  15. /bind R PowExecName Resurrect should work, that's what I have as my bind (except for the choice of key). It will also auto target any dead character (teammate or otherwise), though it will take a second press of the key to activate the power.

    Try using /ShowBind R to verify exactly what is ending up in the bind. My most common mistake is to type PowerExecName instead of PowExecName.
  16. Which proc are you specifically asking about. I don't recall any "Chance to Hit" proc. Do you mean a Chance for Build Up, like Soulbound Allegiance: Chance for Build Up or something else?

    Here's a couple previous questions that might help:
    Soulbound Allegiance build-up in Phantom Army
    Soulbound Allegiance proc question.
  17. Quote:
    Originally Posted by Derangedpolygot View Post
    That said, you were snarky. Stop it.
    I must have a pretty thick snark skin, 'cuz that didn't even rise to the level of snark in my opinion.
  18. StarGeek

    /inspexecname

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

    /inspexecname

    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.
  20. StarGeek

    /inspexecname

    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.