Quote:
Originally Posted by ezigrelnos
[You must be logged in to view images. Log in or Register.]
you want an actual fix to /list? make the hours earned roll over and base the prioritization of your list position on total hours logged at camp
spend 30 hours over 5 days? come back day 6 and you're ahead everyone under you. Are they mad they spent 20 hours and lost their spot? sure, but they can do the same thing and they don't lose their spot. eventually, given enough time spent, you will earn the right to loot (maybe 100 hours? who knows but at least this is FAIR and OBTAINABLE [read:not easy/free])
|
We're just making up our own game at that point ... but the point of this place isn't to do that, it's to recreate EverQuest from 1999-2001.
Look, /list 1.0 started out with the best intentions of doing that. We know exactly what happened in classic when 2+ people wanted a camp, because we have
the GM guidelines from back then:
Quote:
8.2.3 Contested Spawn Complaints
When a complaint is received indicating that a spawn or kill is contested, a disruption investigation should first be initiated according to the procedures of section 8.2.2 to determine if harassment or Zone/Area disruption is occurring. After following those procedures and issuing warnings as necessary, instruct the parties involved in the contested spawn situation to work out a compromise. Then leave the scene.
If another complaint is received involving the same spawn site, another disruption investigation should be initiated. After following those procedures and issuing warnings as necessary, if any of the parties involved were involved in the initial situation, establish a compromise for the parties to which the parties are required to abide. The compromise should be as described in section 8.2.3.1. Any party refusing to abide by the compromise established by the CS Representative should be issued a warning for disruption.
On PvP servers, where players can reach a solution to the contested spawn situation, the CS Representative does not need to require the players to share the spawn.
8.2.3.1
The compromise will require all parties to take turns killing the spawn(s). All parties involved in the contested spawn should be instructed to use /random 0 100 to choose a number. The CS Representative then uses /random 0 100. The individual with the closest number to the CS Representative’s number will be next in the rotation. The CS Representative then bases the rest of the rotation order on how close the other parties’ numbers were to theirs. The compromise established by a CS Representative must be objective and not require the CS Representative to choose one customer over another based on subjective criteria. The CS Representative is the arbiter in any disputes in establishing the compromise.
|
But, we don't have paid GMs with time to do all of the classic stuff described above ... so the devs made /list 1.0 as a way to resolve things automatically without human GMs.
The problem is, back in classic no one stayed at a camp for even 24 hours. Most players' internet connections wouldn't even stay stable for more than a few hours back then!
If we want to do the most classic thing (which, again, is the whole point of this place ... just look at the upper-left corner of your screen) it should be as close to what happened on live as possible. A random roll
was used on live, and it came with an implicit time limit (the camp was assumed to free up within a few hours). If new people contested the same mob after that time, it would result in ... another random roll.
A random /list 2.0 solves all of the (unclassic) problems with people sitting for 24+ hours, trading accounts with each other, etc ...
and it brings us as close as we can get (without paid GMs) to classic.