Quote:
Originally Posted by YendorLootmonkey
[You must be logged in to view images. Log in or Register.]
Think bigger. Devs have access to the entire EQ Emu code. It would be reasonably trivial for them to spawn a dupe mob named Dracoliche with a notrack = 1 flag, and re-code the tracking interface to not display those mobs.
But because the location/movement of the GM-instanced mob is still getting sent to the client, it would show up on SEQ, create a response from the druid/ranger/bard, and then you can nail them for SEQ use as well.
Bag enough people and the end result should be that anyone using SEQ should be scared as shit that they call a raid force in if they see or react to a raid target popping up on SEQ, because they never know if it's a GM luring them in or not.
|
if a tracking class is in the zone Seqing a mob spawn, when they see it on seq I would think they check track just...why not, so when it showed on seq for them but not in game track they might think somethings a little fishy.
on the other note, if we remove the variance and have 3 guilds on lets say naggys spawn point ready to go and he pops, they all engage because theyve been sitting there waiting. If the guild that gets the ks isnt the guild that got first agro, theres going to be punishment, I dont think it would take long before guilds started being a little more reasonable. Of course this isnt the type of behavior we saw in the past...