Honestly, I have limited experience with /list. Just the jboots camp, and even then I had to leave after only a few hours. RL first and all that. So, sure, I will admit my experience is limited.

My understanding is that /list was created for two main reasons. Prevent small groups of players from monopolizing the camps and to prevent /petition spam.I feel the solutions put forward in this thread (forced soloabilty/forced engagement) are simply to0 easy to exploit to be valid solutions to the problem. Increasing the level cap, honestly, doesn't feel like it really does anything, as some classes/players may not be able to solo these camps at any level, including 50.

For the most part, things are very friendly since players have to spend insane amounts of time together in a small space. So you build bonds and want to help each others move up. Theres rarely much ill will.

Its only situations like I describe where this system really takes a downward spiral as it needs to be taken care of now while its still early rather than let the issue continue to fester.

It will get worse and worse if people continue to refuse to help anyone else when the system seems geared to be like Scout rolls.

Maybe there are other solutions that would... incentive player engagement? Maybe make all /afk checks the annoying ones where you have to /list ##### unless you been actively on the agro list for the mob? Maybe make the afk checks even more annoying? /gems till your eyes bleed if you ain't at least tagging the mob?

the obvious solution here is to sit in the safe corner and quote Atlas Shrugged endlessly while reminding people that they should be able to solo the camp before they can get a manastone, maybe that will deter them from interrupting your experience

It's not really any different than killing a raid mob knowing someone with more points will get the drop you want if it drops. You can help kill the mob and advance whoever is in front of you or you can choose not to attend.

Nah, lets take it up a notch and go with Andrew Ryan:D

If the #1 person on the list helped you kill the PHs, what exactly would have changed? Maybe they die a couple seconds faster, which would result in an extra PH/EE over weeks of the camp. Ultimately, no extra Manastones would result.

It's in everyone's best interest to kill the PH. Your solution, even if it's just a rule change, still requires GM intervention to actually enforce - which is exactly what they don't want.

As for requiring anyone on the list to be able to solo, you may as well put the requirement as level 50 to get on the /list for EE and Ghoul/Supp. Even that is too low for some classes.

It seems silly to me to not require the person in the #1 slot to be able to participate in killing the mob. I think a timer for inactivity of killing the ph or named would be beneficial to reduce entitlement and require said person to be capable to solo and/or bring friends to control the spawn.

If this were really classic could you imagine a situation where you enter a camp and someone sitting there invis tells you: "hey buddy - I was here first, but I can't kill the ph so please do that for me. By the way, I'm also entitled get the first rare drop because i was here first." /afk

You can't use an auto-clicker. Some of the AFK checks ask you to type /list 1234 (random number) before you can click the OK button.

best post in the thread