![]() |
|
|
|
#1
|
||||
|
Quote:
Maybe, If you accidentally FTE a mob, where it would have no obvious benefit to your guild to FTE at that time, you may call accidental and wipe it clean. But already we're operating on good faith.. so it's a little complicated. Tracker FTE concedes are really fuckin dumb though. Imagine losing a mob for your whole guild because you forgot where your toon was camped out at last week.
__________________
60 GrandMaster <Aftermath>
Tarew Marr former <Noble Lion> ![]() | |||
|
|
||||
|
#2
|
||||||
|
Quote:
Quote:
Quote:
| |||||
|
|
||||||
|
#3
|
||||
|
Quote:
Completely agreed it's a stupid rule with no relevance today, especially with mages in trips. But I think if you keep the rest of the tracker rules you can get rid of this with no issue and probably don't need to wordsmith much else. Tracker FTE is already horrible on its own. It mostly means your coth mage is dead so you'll be behind. It frequently means you trained other trackers so you may be conceding anyway. No point in further punishing an action that everybody is already desperately trying to avoid. Calling accidental seems reasonable to me. I'm sure there's a weird specific situation I'm not thinking of now that would challenge this but I dunno, guess that's why I was asking about why people wanted to keep it, I can't think of any good reason a tracker fte could be beneficial to a guild. I guess something stupid like having your tracker DA and running one of the non rooted dragons away so other teams can't engage lol | |||
|
|
||||
|
#4
|
||||
|
Quote:
Along the same lines, trying to remove the 2 tracker limit is dumb, because it turns any coth required raid (e.g.: a lot of encounters) into a contest of who can park the most mages. Vanq. already using 3 mages at Vulak for several weeks running, i guess it's obvious why you'd want this: because you assess that you'd be able to park more mages and/or counting to 2 is vry hrd. You mention "good faith" but from where I sit, pretty much no one puts any stock in Vanq. operating in good faith - your leaders and other public facing people frequently demonstrate that you have none. To this point - yes, people are skeptical and/or against the idea because of who proposed it. Detoxx has a long history of being awful, and Vanq. has spent the last year demonstrating repeatedly that it will not operate in good faith. | |||
|
|
||||
|
#5
|
||||
|
Quote:
Juicebox literally cannot type a post without being passive aggressive. Arcler is types in lies and circles to get his way. Why the fuck would you call out Detoxx specifically unless you're sucking Juicebox and Arcler dick? | |||
|
|
||||
|
#6
|
||||
|
Quote:
try to keep up. | |||
|
|
||||
|
#7
|
||||
|
Quote:
| |||
|
|
||||
|
#8
|
||||
|
Quote:
| |||
|
|
||||
|
#9
|
||||
|
Quote:
The only thing I landed on was what you said--intentionally interfering with another guild's engage. But that's pretty nonsensical and trivial to handle. FTE from a tracker lasts all of half a second while a mage gets one-shotted, and anything that would blatantly interfere with a team's engage would mean a competing raid force is there with substantial fraps. At that point it's literally no different from having any rando member interfere with the engage. What am I missing? | |||
|
|
||||
|
#10
|
||||
|
Quote:
why would you want to open up this can of worms? right now, it's a very clear and easy to apply rule. anything you replace it with is going to be more difficult to apply. certainly the history of this server, and especially it's current M.O., suggests that nuanced rules which require detailed analysis will only be the source of conflict. ambiguity = bad. it's already the case that people argue that anything you do during the course of an FTE doesn't matter, if a new FTE goes out. doing away with tracker FTE almost certain to result in the following: tracker gets FTE; DA's and/or bumps the mob; caps out or dies; new member of same guild gets fresh FTE after mob has been significantly affected; that guild kills mob, argues that it's initial tracker FTE is meaningless because of subsequent yellow text. you say you don't like the lawyerquesting? then stop trying to do away with the simple rules that are easy to enforce. | |||
|
|
||||
![]() |
|
|