macskull

Forum Cartel
  • Posts

    5210
  • Joined

  1. macskull

    Dear Warhamster

    Quote:
    Originally Posted by OPTICAL_ILLUSION View Post
    Yeah I can see where you get the 2-3x more people PvPing figure from.

    Freedom RV just now:

    16 Fight Clubbers in the train

    6 PvPers zone PvPing

    LOL

    *Edit. Scratch that 6 figure. 2 of the 6 were Fight Club outlaws attacking the police. So 4 PvPers zone PvPing LOL

    **Edit. Yes very impressive post I13 numbers for a monday afternoon! LOL

    ***Edit. Can't forget to include the 1 pill box badger.
    Shh, don't hurt his feelings.
  2. Quote:
    While it is not extremely uncommon in MMORPGs to establish patches and minor changes, major overhauls are not often as frequent. Where they have occurred, other trends have been established (i.e. The "Trammel" event in Ultima Online and the "NGE" event in Star Wars Galaxies).
    I chuckled here.
  3. There's no taunt protection, as it were. If you get taunted, the only options for breaking it are to wait for it to wear off, or to break line of sight. Some powers (such as Assault) provide resistance to taunt (i.e. make it last less time) and as of the I13 changes, Break Frees provide taunt/placate resist. In short, one application of a taunt will force someone to target you - or more accurately, taunt will make you the only valid enemy target for its duration. Taunt/Confront does do -range in PvE and PvP but that only applies to Tanker/Brute/Scrapper versions, not the pool versions or the Widow version.
  4. Quote:
    Originally Posted by Prof_Backfire View Post
    I hear Hamidon has unresistable KB attacks as well. Enough to send a rooted Granite tanker flying anyway.
    Knockback from Hamidon is resisted.
  5. macskull

    Us vs Devs

    Quote:
    Originally Posted by Zanthar View Post
    The problem with this idea is the fact that they dont know how to pvp? In all honesty they should have some idea how to pvp if they are going to tinker with numbers, Im not saying they would be great but they should have some idea how it works. after all they nerfed the heck out of it and only some classes are viable in pvp. First hand playing should give them a basic understanding of what toons these days are mostly used to pvp with and possibly given that outlook boost the ones that almost never see pvp action. Of course its a two edged sword as you did point out and it could go either way. Only so much can be done just looking at numbers. But as pointed out it could go either way.
    Here's the thing - they based their I13 PvP changes off internal playtests. When it went to test, very little was changed based on feedback from the people who spent most or all of their in-game time PvPing.
  6. macskull

    I15 broke the

    Quote:
    Originally Posted by Ethric View Post
    What joke? There is no
    Jokes are like cake, they're a
  7. The computer service/sales shop I work at uses AVG and MalwareBytes, and occasionally Advanced SystemCare. For the few times we've had customers request some sort of web filter, we've found K9 has worked just fine, though it is a bit stringent.
  8. Quote:
    Originally Posted by Fleeting Whisper View Post
    The only way for those in-set protections to be bypassed is to be hit with non-resistable KB (which is above mag 10), which is extremely uncommon. I think UXBs in a Rikti invasion are an example.
    UXB's and the Nuclear Blast temp power from Warburg are the only powers that have irresistible knockback, I believe.

    That being said, you'll be safe from 90% of what you come across in PvE with 4 points. There's very little knockback from AI entities in the 4-12 range, so there isn't much 8 points will save you from that wouldn't already be covered by 4. Hamidon's yellow mitos deal mag 13 KB, and some AV's deal knockback that'll take out pretty much any squishy (Siege has some attacks with high-mag KB, and Recluse has some KB power or another that managed to bypass my Rad/Psi's 21 points).
  9. Quote:
    Originally Posted by MurderousMalk View Post
    What do you think black rad blast can be...hehe
    Rad Blast, colored black.
  10. macskull

    Trick Arrow Yay!

    Fire/TA was loads of fun in closed beta despite the issues that Trickshooter mentioned.
  11. A well-played Pain MM is one of the hardest-to-kill builds in the game right now. Even a badly-played Pain MM is still tough to kill - the set's just that good on an MM.
  12. I'd wanted one of these procs for my Fire/Kin and Fire/SS (low damage caps and all that, figure I might as well get more mileage out of 'em) but at the going rates they're just not worth it.
  13. macskull

    I herd

    Yes, for one last glorious weekend, there will still be "power" in "powerleveling."
  14. Quote:
    Originally Posted by Ignitros View Post
    What about the new changes to Psi? I hear that WoC is a pretty good combo. Since it's not in MIDS I can't really look at a potential build yet so any thoughts?
    Pretty much what Liberty said - it's not a very good power at all in practice, even if it sounds good on paper. My only toons with it use it as a set bonus mule for the (relatively) cheap purple confuse set. Still better going with Stone unless you know you're going to be fighting a lot of mez-heavy enemies.
  15. Quote:
    Originally Posted by Tokyo View Post
    Name calling is cute.
    So are small children, keep it up. Nothing's making you read the threads in this section - that you feel the need to comment on them says much more about your level of maturity than it does anything else.
  16. Quote:
    Originally Posted by Tokyo View Post
    Can we get these old threads deleted? They make you PvPers seem like tragic optimists.
    Better to be a tragic optimist than a complete ******* moron.
  17. Hm, you might have more luck posting this in the Mac subforum. If all else fails you might just have to download the test server installer again.
  18. FYI, the Catalyst 9.8 drivers under Win7 Professional x64 broke my Sapphire HD4850 - the entire system would just do a hard crash and I'd have to reset it (stock speeds, Zalman aftermarket HSF/ram coolers). Reverted to 9.7 and problems solved.
  19. After some digging around, it might be due to faulty drivers (crashes were sporadic under Catalyst 9.7 but now they're happening on every boot under 9.8). I replaced the stock heatsink and RAM coolers with Zalman HSF/coolers but again I had no problems with them under XP. Thinking I'll see if I can't uninstall the video drivers and try again from scratch. Not finding much information on this via Google either - someone suggested disabling Aero or even disabling the second processor core, but I'm hoping it's something software-related that I can fix without having to lose functionality.

    EDIT: Did a system restore to before I installed the Catalyst 9.8 drivers and I'm now back in working order.

    EDIT EDIT: Nevermind, locked up again - just took a bit longer.
  20. Few quick questions...

    1. What model computer are you using? If you're not using an Intel-based Mac (basically, any Mac made since 2006) CoH won't work.
    2. What version of OS X are you running? The test server copy uses an updated version of Cider that won't run under 10.4 (Tiger) - you'll need 10.5 or 10.6 (Leopard or Snow Leopard).
    3. Can you copy and paste the error message here? Someone more knowledgeable than I will probably be able to help you out.
  21. Interesting turn of events here... since I installed Windows 7, the computer's hard crashed a few times (never did it under XP). It was usually a few days between crashes and wasn't such a big deal since I could just reset it and be on my merry way. Yesterday, I got another hard crash, so I reset it and started my apps back up only to have it crash again. Did this four times before I finally powered down for the night. Woke up today, gave it another go, and it crashed a few times again. Pulled the memory and video card, reseated them, and tried it again, and it ran for a minute or two longer than before, but crashed again. I've got it running in safe mode right now and haven't had it crash on me yet, so I'm not sure what the deal is. Guess I'll just start axing startup items one by one to see what the problem could be (I have a feeling it might be ATI's drivers since that's the only change I've made in the last few days).