Q:
Wynd Cloud | Fierce N Licious
Q:
Hi my team has been practicing for the DnT trio tourney and we are unsure of some of the rules on the gw2dungeon speed clear. I don’t want to give away some strategies so I will be vague so I apologize in advance. So you know how if you wall Lupi, he will not perform some of his skills. Now there is another boss in this game where if you abuse positioning he will only use one of his skills. He is technically not disabled since he is using his skill but that spot basically makes him unable to use his deadly skills, is that considered safe spotting?
A:
I would say boss must be able to use his offensive attacks. Does that sound fair?
(edited by Wethospu.6437)
Wasn’t doing the Warden in TA on the tree a similar situation that was disallowed?
I think the warden in TA is completely disabled, he just sits there. But this boss is still using 1 skill. So then the rules becomes ambiguous.
Ahh for some reason I thought the warden just lost his big hitter.
If you are talking about cm p2 Turmaine(endboss) you are not allowed to bug him in the barrels/on the rock/on top of the house. It completly disables the boss and it was discussed on the last meeting to be banned from trio.
If its not that boss please specify wich boss it is.
You answered your own question. And unless you specify we cant really say. :P
If you are talking about cm p2 Turmaine(endboss) you are not allowed to bug him in the barrels/on the rock/on top of the house. It completly disables the boss and it was discussed on the last meeting to be banned from trio.
If its not that boss please specify wich boss it is.
He still throws his grenades so its not completely disabled. But if that was agreed to be banned at the meeting then it seems it needs to be added as a path specific rule.
(edited by spoj.9672)
Arguing semantics here but wall doesn’t stop Lupi from doing Frenzied Blast.
Was it agreed during the meeting? I don’t really remember, but the boss isn’t completely disabled; he still does his AoEs and I would argue that it should be allowed. And honestly, there are so many places you can "bug" him that it seems more like an annoyance having to focus on not doing it.
Was it agreed during the meeting? I don’t really remember, but the boss isn’t completely disabled; he still does his AoEs and I would argue that it should be allowed. And honestly, there are so many places you can “bug” him that it seems more like an annoyance having to focus on not doing it.
Yeah i personally think it should be allowed. If it wasnt mentioned in the meeting then its allowed for the time being.
Was it agreed during the meeting? I don’t really remember, but the boss isn’t completely disabled; he still does his AoEs and I would argue that it should be allowed. And honestly, there are so many places you can “bug” him that it seems more like an annoyance having to focus on not doing it.
Yea I would like that to be allowed but im pretty sure Nike said its banned from the trio tourny as it disables the boss. I don’t remember if we voted on it but from my PoV I agree with you, it should be allowed.
I’m not the final authority. Weth and the other approvers are the ones who have to make rulings.
It would be nice if we had 1 hour of development time weekly for dungeon related stuff. So we wouldn’t have to keep guessing so much.
Anyways all these things will be decided case by case. If you want 100% answers you have to be specific. My goal is to try keep things fun which means not restricting stuff too much but also not allowing things going too one dimensional.
Regards Turmaine, is there a reason why it shouldn’t be allowed? He constantly dashes towards you and if there is something on way he gets stuck. It feels weird to make a boss like that and then put obstacles on his way.
(edited by Wethospu.6437)
Not affiliated with ArenaNet or NCSOFT. No support is provided.
All assets, page layout, visual style belong to ArenaNet and are used solely to replicate the original design and preserve the original look and feel.
Contact /u/e-scrape-artist on reddit if you encounter a bug.