![]() |
#31
|
||||
|
![]() Quote:
Its clearly an oversight that there's no mention to participate in any kill even as #1 of the list. Just think for a second what #1 even represents: it's now your turn at the mob. Nothing crazy has to happen here coding wise to check encounter logs, just add one sentence to the List Ruleset: " If you are #1, you must participate." If you were a total dick for 30+ hours and by the time you reach #1 no one wants to help you, well thats your bed you made [You must be logged in to view images. Log in or Register.]
__________________
Eratani / Cleratani / Eratou / Stabatani / Flopatani / Eratii
| |||
|
#32
|
|||
|
![]() Number one should just claim to be a real life female who is too timid and terrified to unhide at such a dangerous camp. The rest of the list would bend over backwards killing as many spawns as it takes.
| ||
|
#33
|
||||
|
![]() Quote:
| |||
|
#34
|
|||
|
![]() Im glad it took you this long to see the errors in this system. I dont get why anyone would wanna help the #1 guy. I ran into this at Jboots (a level 25 bard who could NOT solo this camp normally) and DE mask camp(level 35 druid who COULDNT solo this camp, too). The person ahead of me could sit around the corner in a non agro area waiting for someone else to do the leg work while being assured they get the list item upon it dropping. Nothing will fix this issue as it wasn't tested long enough to really fish out the issues that are coming to light now. Id like the AFK check to also do a PH check. If the PH remains up (or named) and you fail to kill it in the 10ish min window, you are tossed off the list and have to rejoin. Welcome to green.
| ||
|
#35
|
|||
|
![]() Maybe #1 is getting off on the fact that he's rustling everyone and just ignoring him and killing the spawns is the worst punishment you can offer.
| ||
|
#36
|
||||
|
![]() Quote:
| |||
|
#37
|
||||
|
![]() Quote:
glad it seems like you got your items despite your whining and crying | |||
|
#38
|
|||
|
![]() You sign up for a camp, you should be a part of it.
We had an enchanter yesterday also refusing to engage bc he was keeping faction and said he would only begin to participate when he felt his Manastone was within 24 hours. Faction hits before then would be a waste. (its 2 faction hits each hour btw)
__________________
Eratani / Cleratani / Eratou / Stabatani / Flopatani / Eratii
| ||
|
#39
|
|||
|
![]() Is it really surprising that people are automating AFK checks and not participating in kills?
| ||
|
#40
|
|||
|
![]() I still feel that forcing players to engage is not a reasonably demand. HTing SKs is a great example, as mentioned earilier. Its not the lvl 35 ones you need to worry about. A pair of lvl 50 SKs, guilded with Mr. /list 3 can invis down and make a fairly good attempt at not just KSing, but killing the mob before anyone has a chance to agro. Yes, spamming "target nearest" and auto attack is a thing, no doubt, I don't think it would be required. And even then, a small distraction at the wrong time? Ya done, go home, they got ya.
The other issue the folks are interested in is that you should be able to solo the mob if you /list for it. I disagree. Not all classes can solo well. Just because a warrior can't use mana stone does not mean they shouldn't be allowed to /list for it. While I do agree with folks saying everyone should help out, if the warrior fears for his life if he is the first to engage and everyone else is just gonna stand by and watch him die so they can move up the line, well, I wouldn't engage first either. Saying solo it or go home is pretty crazy to me. Honestly, can a crap geared warrior even solo EE at 50? | ||
|
![]() |
|
|