View Single Post
  #73  
Old 05-07-2026, 09:49 AM
cd288 cd288 is offline
Planar Protector


Join Date: Apr 2018
Posts: 4,512
Default

Quote:
Originally Posted by Wayward [You must be logged in to view images. Log in or Register.]
No, if the lowbies decided to camp within aggro range of the Spectre's spawns it would be their fault.

Someone else here said it, but the rule has always been once a mob has been moved from it's spawn point (unless it's a roamer), any accidental or intentional player deaths caused by that are considered trains.

Static mobs won't aggro anybody if nobody's in aggro range. It's not until a player moves them from that point. This has historically applied to raid content, but it can be extended to normal content as well.

Whether the train is intentional or not is another argument, but re-defining a train based on intention is stupid. There's accidental trains, which is seems like what OPs initial problem was (compounded by a dickhead player who can't admit to accidentally training someone and apologizing) and then there's intentional trains like Chortles epic Howling Stones train that got him banned.
Again, your example isn't analagous. Where OP sat on the Garg island is nowhere near as close to the Spectre spawns like sitting by the tower in Oasis would be. I have spent plenty of time on that island. It's completely easy to be aware of where other players are and not quad over them. The staff have always ruled that if you quad you have to be aware of where the players in the area are.

In this case, OP actually made it easier on the guy because he went and sat far out on the edge of the island away from everything. He wasn't out killing gargoyles. Point being, if some lowbie is killing Gargs and you quad the Spectres and run them through the lowbie and he dies, the staff will blame you for it plain and simple. Your opinion on it isn't relevant, it's just the rule.

At any rate, to take this back to the original discussion, Slidein is just and idiot who doesn't understand mechanics. If he had, this would have never been an issue in the first place.
Reply With Quote