![]() |
#82
|
|||
|
![]() I'd like to believe this would already be addressed if it wasn't an issue of changing source.
__________________
![]() Jack - Server First Erudite | ||
|
#83
|
||||
|
![]() Quote:
| |||
|
#84
|
||||
|
![]() Quote:
/List allows me to not clear. Camp rules do not. | |||
|
#85
|
||||
|
![]() Quote:
__________________
EQ Emulator population tracker - https://unixgeek.com/eqemu.html
| |||
|
#86
|
|||||
|
![]() Quote:
Quote:
| ||||
|
#87
|
||||
|
![]() Quote:
| |||
|
#88
|
|||
|
![]() *getting pop corn*
Laughting hard at all the threads with people complaining about /list system. | ||
|
#89
|
|||
|
![]() In the old days, when you were on the list for a camp, you couldn't go AFK for long stretches of time, right?
I think the /list command, with its AFK checks, is just automating how the old lists worked, when players were enforcing it amongst themselves. Is this correct? If so, I think there's little chance of convincing them to change it the way people are suggesting. | ||
|
#90
|
|||
|
![]() The main thing /list is doing is prevent groups or guilds of players from completely locking down legacy items for financial reasons - that's what the GMs wanted to stop. It's a way to do so without GMs having to be involved, otherwise they would be getting non stop petitions.
If you weren't around for Kunark launch, some guilds did this for weeks/months on certain mobs that had drops for access to zones like Howling Stones and VP.
__________________
Green
Tofusin - Monk <Force of Will> Manowarr - Druid Blue Tofusin - 60 Monk <BDA> Shiroe - 60 Enchanter Manowarr - 60 Druid | ||
|
![]() |
|
|