/List Server Ruleset Should Consider Tweaks

[bubur]

Originally Posted by Magerin [You must be logged in to view images. Log in or Register.]

Welcome to green.

more like welcome to your and grakken's weird imagination land

glad it seems like you got your items despite your whining and crying

[Fammaden]

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.

[Erati]

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)

[Argh]

Is it really surprising that people are automating AFK checks and not participating in kills?

[Cuktus]

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?

[Erati]

Originally Posted by Cuktus [You must be logged in to view images. Log in or Register.]

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?

Have you personally experienced this situation ?

It's pretty awful. Requiring at least the #1 position player to take some responsibility towards their turn is the minimum that should be expected is my only point. People outright refusing at #1 is a joke and needs to be adjusted in the ruleset.

[cd288]

Originally Posted by Erati [You must be logged in to view images. Log in or Register.]

Have you personally experienced this situation ?

It's pretty awful. Requiring at least the #1 position player to take some responsibility towards their turn is the minimum that should be expected is my only point. People outright refusing at #1 is a joke and needs to be adjusted in the ruleset.

I agree with that point. I don’t care about others in the list but if you want to do the list then you need to be able to solo the mob should the situation arise

[stewe]

I've said it before and ill say it again, THE LIST ISNT GETTING CHANGED, they put it in for less work not more coding work, you dont like it dont go to those camps, just like you cry that you arent obligated to kill the mob for them, they arent obligated to help you kill the mob either, once i get a few more lvls i plan on chilling in a corner on the list and watch shows etc and if someone sends me tells bitching they get put on permanent ignore, simple solution to crybabies.

[Erati]

Originally Posted by stewe [You must be logged in to view images. Log in or Register.]

I've said it before and ill say it again, THE LIST ISNT GETTING CHANGED, they put it in for less work not more coding work, you dont like it dont go to those camps, just like you cry that you arent obligated to kill the mob for them, they arent obligated to help you kill the mob either, once i get a few more lvls i plan on chilling in a corner on the list and watch shows etc and if someone sends me tells bitching they get put on permanent ignore, simple solution to crybabies.

No one is talking about a code change.

They just need to add 1 sentence in the rules: "Position #1 must participate in their kills or potentially be removed from their spot"

Out of all the positions on the list, being #1 and not doing a thing is a total flaw of this system.

[Erati]

Imagine being #4 for over 30+ hours killing PH as you watch a guy never move an inch the entire time slowly rise into the top position.

Then when that guy hits #1, he still refuses to budge.

This is within the rules and acceptable in some peoples minds.

Shout out to Thesafux - he battled PHs for so many hours and was forced to be behind an AFK automater. Can't imagine how frustrating that has to be watching a guy get a MS when he refused to help anyone else prior.