Results 1 to 7 of 7
  1. #1
    Community Member
    Join Date
    Aug 2009
    Posts
    109

    Default Solution to punishments for exploiters

    Facts:

    1) Most exploiters tend to be the people who know the game well (too well, in fact...)
    2) Most devs seem to have no idea how the game gets played (last DDOcast had several devs talking about how they spend HOURS running coal chamber). No offense devs, this makes you bads (but we still love you).


    Solution:
    -Instead of not being allowed to play for two (four) weeks, exploiters should be forced to group with devs and show them how to play the game (the way that goods play the game---not the way fresh offa da boats korthies play).

    Benefits:
    - Exploiters get punished (no, stop, don't jump ther....DING!)
    - Devs get lessons from top players on the servers and can make better decisions about how to make changes to the game we'd like, what kinds of things are challenging vs. boring vs. fun for us, and what kind of loot we'd be looking for.


    -Purr


    PS we do love you, devs, but seriously, 2 hour coal?

  2. #2
    Community Member toaftoaf's Avatar
    Join Date
    May 2013
    Posts
    24

    Default

    maybe they are playing the game on a tandy. just like the ones they use for the servers .

    or maybe they are playing with no mouse (that would slow us down)

    maybe they have to walk down the ramps because they dont have a FF item

    trying to think of reasons why it would take 2 hours..

  3. #3
    Founder & Hero
    2016 DDO Players Council
    Uska's Avatar
    Join Date
    Jan 2006
    Posts
    0

    Default

    uMM no cheating doesnt make you a top player it just makes you a CHEATER! AND SOMEONE WHO SHOULD BE BANNED BANNED BANNED!
    and banned again when they make a new account under a new name.
    a top player is someone who can do it well without cheating


    Beware the Sleepeater

  4. #4

    Default

    Cheaters always have the option to report their cheating ways, but they don't for a reason. They need no special compensational use.

  5. #5
    Community Member lugoman's Avatar
    Join Date
    Sep 2009
    Posts
    910

    Default

    I'm all for punishing exploiters, but forcing them to group with the devs is cruel and unusual punishment!

  6. #6
    Community Member Ivan_Milic's Avatar
    Join Date
    Jun 2010
    Posts
    3,620

    Default

    This duping bug was so easy to do that anyone could have done it even on accident.
    Some exploiters got perm banned, idk how turbine decided who gets perm and who gets temp ban.
    IF turbine devs wanted to learn the game they would do so, but this is punishment for both the devs and players.
    Last edited by Ivan_Milic; 11-05-2013 at 07:41 AM.

  7. #7
    Community Member voodoogroves's Avatar
    Join Date
    Oct 2009
    Posts
    8,366

    Default

    Quote Originally Posted by Ivan_Milic View Post
    This duping bug was so easy to do that anyone could have done it even on accident.
    Some exploiters got perm banned, idk how turbine decided who gets perm and who gets temp ban.
    IF turbine devs wanted to learn the game they would do so, but this is punishment for both the devs and players.
    Most of the "real" exploiting/cheating isn't really an in-quest thing. I suspect the devs would be bored sitting in the bank watching party chat as people try manipulating bags, etc. Oh and then let's run to the Fatespinner next ...

    Sure, using things that weren't intended to be used in-quest makes it easy - but there is little to learn there (except that cocoon in heroic is handy, energy burst is way too stupid good and it's funny when you see someone with a Shiradi or freaking Reign twisted in).

    The devs would learn far more by just running with moderately-smart folks on a TR train.
    Ghallanda - now with fewer alts and more ghostbane

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

This form's session has expired. You need to reload the page.

Reload