![]() |
|
|||||||
![]() |
|
|
Thread Tools | Display Modes |
|
|
|
#1
|
||||
|
Quote:
Thank you! | |||
|
|
||||
|
#2
|
||||
|
Quote:
On my list of things to do is a brief write-up outlining proper procedure when handling a dispute, from the infraction taking place through to a completed dispute. Hopefully this will make staff expectations for dispute mediation more clear | |||
|
Last edited by Derubael; 10-21-2014 at 05:02 PM..
|
|
|||
|
#3
|
|||
|
Again, to make sure we are all on the same page, my personal interpretation of that particular statement by Sirken, based on how rule changes are usually made and information is disseminated among the Senior Staff - as well as the context of the statement and being fortunate to know how Sirken thinks, is that this was not a hard rule, and instead a suggestion.
I personally don't have any problem with implementing the aforementioned rule if you all feel that it's necessary (and don't just make your decision based on wanting to get TMO in trouble), then I don't see the harm, though the benefit doesn't seem to be huge either, and we should all keep in mind that the more rules we add, the more nuances and exceptions that new-comers to the raid scene have to be sure they don't violate. Maybe my trust in the average guild/raid leaders ability to read a bunch of forum threads or receive clear instruction from their peers is less than it should be, but I am already concerned at the increasing number of circumstantial or mob-specific rules that seem to be "needed" for guilds to stay in line. I think the "don't engage targets with your trackers" rule should already cover this one pretty thoroughly. Most importantly, you will all need to wait for Sirken's clarification. He's also extremely busy this week and may take some time to respond, but obviously until he does, it is probably best to follow it as if it's a literal set in stone law just to be safe. I still find it highly unlikely that he intended to add more restrictions on where people can be and where they can't be, as this is something we really don't like setting limits on wherever we can avoid it - this is something we've both been pretty clear about, if not in public, than certainly in our own private discussions. As a final note, even if we are to assume that this rule is active and was active at the time of these screenshots, there still simply isn't enough here to corroborate Catherine's explanation or damn TMO to <insert community chosen torture here>. If people are getting FTE with trackers, even if they quickly die and drop aggro after it happens, people should start fraps'ing that and compile a thread here in raid discussion to highlight that it's an ongoing issue. If it's as large a concern as this thread seems to suggest, rather than one or two isolated incidents that can easily be mediated between guilds rather than force staff intervention, it's something we can deal with in a fashion that doesn't require the creation of more rules. I would greatly prefer this to the alternative - creating more and more restrictions and rules to try and enforce... rules that we already have in place. | ||
|
Last edited by Derubael; 10-21-2014 at 10:56 PM..
|
|
||
|
#4
|
|||||
|
holy fucking nerds.
listen, essentially we (staff) are saying the same thing. if nothing pops i obviously dont care where people are, because no harm no foul. but if the mob pops and you have trackernerds on the spawn spot, their trackernerd will/should get aggro, and as such they would be breaking the "trackers can't FTE" rule. its really getting ridiculous the way some of you are picking apart staff posts to benefit yourselves. all of the raiding guilds need to stop trying to game the system and play the game within the rules, or you're gonna have a bad time. <3 Sirks
__________________
Ever wonder what Braknar does around here? - https://youtu.be/WTtFXBgggpI
Sirken's Twitch Stream - www.twitch.tv/sirken_ Quote:
Quote:
![]() | ||||
|
Last edited by Sirken; 10-22-2014 at 12:03 AM..
|
|
||||
|
#5
|
||||
|
Quote:
| |||
|
|
||||
|
#6
|
||||||
|
Quote:
__________________
Ever wonder what Braknar does around here? - https://youtu.be/WTtFXBgggpI
Sirken's Twitch Stream - www.twitch.tv/sirken_ Quote:
Quote:
![]() | |||||
|
|
||||||
|
#7
|
||||
|
Quote:
__________________
https://www.asgardguild.net Whoever wields this hammer, if he be worthy, shall possess the power of Thor! -Odin
https://www.twitch.tv/artaenc I stream other games on here also like Monster Hunter World Guild Leader of <Asgard> The home of the gods! Lightyear/Artah | |||
|
|
||||
|
#8
|
||||
|
Quote:
Do you guys have your own established rule regarding the CotH'ing of players by tracker-mages when a target spawns? If no, there are no rules against this from a CSR standpoint. Sirken had specifically asked me if this was legitimate earlier and I was unavailable to respond but as I stated above, there are no rules against this at this time, unless those rules are player-made. | |||
|
|
||||
|
#9
|
||||
|
Honestly, I do not what is going on here anymore, because "That being said, it is absolutely not ok for trackers to be parked on raid spawn locations" did not have any qualifying adjectives like "kos trackers". Sirken's statement was clear: no trackers in range, and hence Taken (rightly or wrongly) being upset when they perceived a tracker(s) were in range.
Clearly, folks were trying to inch up on the mob, and rather than the refs calling off-side we are now all going to have to go faction in MM? First, let's give some props to the prediction on 07/14/2014: Quote:
Do we really want to just limit the scale of poopsocking? I hope not. Next, think about those poor GT folks or Dojo guys when they were perplexed at the web of raid rules - now you want them to faction up a bunch of dedicated CoH trackers? I suggest going back to the problem and seeing if we can fix the original issue: the ball first got moved when we allowed CoH FTE's. That spawned CoH ducking and 16 poopducksocking by 2 trackers. Now, we (possibly) are inching the ball a bit closer by allowing factioned coh duckbots... Can we agree to fix CoH ducking, and then this issue will go away? Trakanon can stay the same or we can all just clear down to Trakanon - whatever you guys prefer. Next, and this is for the staff, who I want to thank again for putting up with all this BS lawyering, and for putting in their free time to police the mess. I know it is frustrating to make a rule and then have everyone pick it apart. It must feel like folks are nitpicking. However, I believe that communication via text is very difficult, and what is really happening is the raiding guilds are trying to fully understand the scope of the rule. I would humbly submit that before any new rule is set in stone that you give the various guilds 1 week to do their rules lawyering best to see if they can find any loopholes / clarification so we don't have to go down this thorny road each time. Secondly, and this is a shameless plug, I would like to start thinking about Velious, and start to hear about any new rules the staff would like to work on prior to release. And i do have a horse in the race: Ziglark Whisperwing. At some point fairly soon, can we sit down and discuss what potentially will be a mess in Velious? Again, thanks for your patience, and effort on our behalf.
__________________
Drakakade ~ Divinity
| |||
|
|
||||
|
#10
|
|||
|
C/R Rotation, 100% FFA on simulated respawns.
puts this problem to bed entirely. | ||
|
|
|||
![]() |
|
|