Incorrect login detailsYour account is permanently bannedYour account has been placed under a protective block for security reasons. Please contact support.Your account has been deletedYou have reached the limit of authorised attemptsYour account name has been blacklistedThis Ankama account is protected by the Authenticator.
Open the Authenticator application.
Select your account.
You will have 30 seconds to retype your account information.
The Troyle has said that surrounding Dragon Pig with tools such as beacons or dolls will be considered as abuse.
HOWEVER as long as Cra can place beacons exactly in some spots (same for panda and barrel), the Sadida cannot make dolls "move away from the UB", even if controled the dolls might stay locked, and making Sadida need to control every doll on every turn only kills the whole point of even using dolls there. That's like making whole class unable to fight with its potential, as Sadida is based on its summons. Yes we have Lone Sadida mechanic, but guess what: not all Sadidas level this passive. And it still doesn't change the fact that we cannot use our build as summoner.
As long as i agree that abusing bug is wrong, i have to ask Ankama to fix this issue and next time to make enemy's AI work well when surrounded with summons of players, because it really makes Sadida class not welcome in this UB fight.
The whole of players choosing to be summoner Sadidas is to have access to multiple summons, but using them in UB fight will be considered as abuse of bug.
Now may i ask if there is planned compensation for players with ability to summon of some sort? I mean... i doubt there is but it is clearly bad from Ankama side.
Now what if some players doesn't read forums? And look they are using dolls to attack the Dragon Pig, and it turns out the dragon pig got trapped somehow. Now they will get punished for playing their own class normally!
Seriously Ankama, first was the issue with Voodoll on Black Crow, now is the issue with Dragon Pig. I am afraid to do any UB fights as Sadida player, in fear i will get banned or get some other penalty like all items wiped.
Don't get me wrong, i don't want to abuse bugs. All i want is play normally. And using summons to trap someone is normal gameplay of Sadida class.
Therefore if this bug will be fixed, please do inform us that we are again free to try to trap Dragon Pig or play normally even if Dragon Pig will somehow get trapped anyway.
Still what i don't understand is that Ankama want to make us always take sacrier/feca (or in short future Foggernaut) just to TANK the dmg, and Ankama doesn't want to allow summoner classes to use their summons to TANK. This seems ridiculous. Why you even invented system where players can summon something, if every time you find it as abuse?
Face it: you have failed to revamp Dragon Pig, AGAIN.
Just... fix it... and make it not ever happen again as i don't want to play the game knowing that my normal gamplay might be considered as abuse and then i get penalty.
Note: i haven't abused this spell. In fact i am not even subscribed at this time. And actually the fact why i am not subcribed is also because of this. I am not gonna sub if my class will keep getting punishments for playing.
Why you dont call healing in UB fight as abuse? Or reducing boss resist or throwing boss - why its not abuse either? I mean... hello? It's basic mechanic, right? And so is the ability to summon.
Next time please check UB's AI in such situation and make sure these bosses can still fight. It's not players fault that the boss is not working as it should.
Maybe just close Dragon Pig again until this issue is fixed so that every class will have the same chances/the same amount of times to fight it. This time with no abuse possible please.
There's been a lot of uproar about it recently, but in my opinion it's very clear. Players are put in a task to beat DP; they have all the tools the developers gave them and they're free to use them, it's a sandbox game. If they don't use the ways and tricks Ankama wanted them to use it's not their fault and it's Ankama's task is to fix it. DP should be beatable only using the intended strategy. It doesn't matter if the mechanic used to abuse looks fair or not, it's completely irrelevant. Ankama should treat every way of beating DP which is not the intended strategy equally. The explanations and favorizing some tactics is completely absurd. If the seed abuse was used to create a square box for DP where he moves and hits some fake target it makes it a not sanctionable strategy? Because the fooled AI does something? The AI is still fooled and it has completely no justification to excuse such a strategy. It's a phenomen opposite to sensible thinking. Player shouldn't intend to make the boss at least do something against them because the script is invalid.
Manyfaces|2013-09-22 22:58:59Question when you trap the dp is it able to do anything?
From what I hear, the Dragon Pig isn't able to actually deal damage on players (Note: He doesn't "skip" a turn, but rather uses buffs on himself and then ends the turn). From what I hear, this sounds not so much of a bug, but rather poor mechanics. In my mind, it seems the dragon pig should be able to be boxed in by summons, at which point he'll just start using some long-range non-LOS moves.
In short, using cra beacons, dolls, barrels, etc. should be considered a legitimate strategy against all UB. It's Ankama's fault for not implementing some attack that damages/destroys obstructions and/or some long-range attacks.
**I emphasize this point because I believe this is what separates "exploiting a mechanic" from bug abuse. If the DP simply automatically skipped his turn, then it would be pretty likely to be a bug. However, since this is just poor mechanics for the boss fight, it's more of an exploit since you're using it to your advantage. Regardless if this exploit is fair or not, players shouldn't be punished for it (i.e. getting banned, stat reduction, etc.). However, in this case, it might be OK to simply delete rewards associated with this.
It is basically Ankama's failure to resolve this, though.
God, the whole point of fighting those kinds of bosses is to win. People summoning and placing machines is going to be a big part of that, unless you do something like giving the boss an ability to eat the summons and heal, or maybe turn the attacked summons into an enemy.
I'd always thought that getting a boss to where it can't attack for a turn is a wonderful and fun challenge, and I actually try to do that as much as possible on all 5 classes I currently play.
If its an abuse from the perspective of Ankama then fine, fix it. But don't come whining and dripping snot all over complaining about how unfair it is that players come up with ideas to let them win and have a shot at your really crappy drop% rates.
As far as I can observe jailing him would be a legitimate strategy if his mechanics to counter it were working properly. But since it abuses his AI to just use Bacon Run and pass, it's something that needs to be worked out before Ankama acknowledges it as such.
I think this situation will be panned out with the next update, and you'll be able to surround him thusly without his AI breaking and it ending up being considered bug abuse.
Yes they messed up the revamp. What we hope is that they don't miss any details whenever they do change Dragon Pig to rectify this.
The problem with DP is that there is only one legit way to win. It's like a riddle you have to solve and if you don't get the answer right yet you still win you can get sanctioned. It's not our fault that Grou didn't consider multiple answers for his riddle.
Asthis|2013-09-23 05:57:31Because that's the way DP was designed. :\
"Designed" Yeah...no. There is nothing designed about this and what is worse is the fact that their so called design always leaves players in the dark. So no wonder all kinds of "wrong" strategies are being used.
What always baffles me most is how they still screw up even the map design. God damnit Ankama people love to abuse sketchy border tiles. Just make it a rectangle with the debuff tiles in every single spot. Many problems solved already...