![]() |
|
|
|
#1
|
|||
|
Just a wild suggestion for the /list element.
Players accumulate "camp" time towards the list in the following ways: - For every hour (and minute) active at these particular camps accumulates time towards the "camp". - For every hour (and minute) offline from these particular camps accrues a fifty percent penalty loss per the amount of time offline. - The order of the /list is based upon whomever has the greatest amount of "camp" time accumulated. Example: Four players all begin camping at the exact same moment. I will use hour 32 as the end point for my example. - Player #01 does a 24 hours stint and logs for 08 hours. (24-(8/2)) = 20 hours. - Player #02 does a 32 hours stint and does not log. (32-(0/2)) = 32 hours. - Player #03 does a 04 hours stint and logs for 12 hours, then returns for a 16 hour stint. (04-(12/2)+16) = 14 hours. - Player #04 does an 08 hours stint, logs for 08 hours, then does another 08 hours stint before logging off for 08 hours. (08-(08/2)+08-(08/2)) = 08 hours. Thus the order of the list at the 32nd hour would be: Player #02, Player #01, Player #03, and Player #04. Let's say Player #05 started at hour 16 and was in the middle of a 16 hour stint. Thus he would have accumulated 16 hours and thus would fall into the /list after Player #01 and before Player #03 at the original 32nd hour. It may sound a bit confusing, but you reward those players that put in the time while giving them an option to recollect themselves in real life without losing everything they built up over the long haul. Over a long haul, one may collect enough "camp" time to keep the first /list spot, even with breaks. | ||
|
|
|||
|
#2
|
|||
|
After 27.5 hours between manastone drops, one just dropped for Pine. Soo happy for him!
| ||
|
|
|||
|
#3
|
||||
|
Quote:
| |||
|
|
||||
|
#4
|
|||
|
If the ph isn't being killed for some period of time, everyone on the list should be kicked off and blacklisted for a bit.
| ||
|
|
|||
|
#5
|
||||
|
Quote:
__________________
Mr. Irrelevant
| |||
|
|
||||
|
#6
|
|||
|
The law of unintended consequences.
__________________
Quinok - 44 Shaman <Europa>
Celador Elysius - 57 Beguiler Writing P99 articles at Where The Monsters Are | ||
|
|
|||
|
#7
|
|||
|
ive gotta say this is concerning eh. don't make any changes, just let people afk so they can actually look after themselves.
| ||
|
|
|||
|
#8
|
|||
|
Was the drop rate changed? In the last week or during the launch of Teal?
My recommendations 1. You must be on the engage log, else you cannot loot and it passes to the next person on the list. Ex. If you are #1 and aren't on the engage log and MS drops, #2 can loot, and #1 retains position to try again next time. 2. 30 Seconds or less response on AFK checks. Like any other camp in the game. 3. If you disconnect, log, or leave the area you get knocked off the list (like any other camp). Maybe this is too harsh, but at least reduce the amount of time from 900 seconds to 300. The list will turn over more often, but it won't feel as painful losing your place | ||
|
|
|||
|
#9
|
||||
|
Quote:
Also, I don't really see the point to your number 1. Most people on the list are participating in downing the spawn, especially if they are at the top of the list. And if they're not, who cares. Others will still help kill the spawn regardless of whether the person at the top is on the engage log because the faster the spawn and PHs are killed, the faster the list moves. | |||
|
|
||||
|
#10
|
|||
|
ANNNND I was just kicked off of the list after over 50 hours of being on it, being on almost if not EVERY single PH and eye encounter log.
I was literally typing in /say talking to the other guys here, and in the middle of a sentence got the 'You have been removed from the list for failing AFK checks'. Checks I never even got on my screen. This is heartbreaking. I can understand failing AFK checks for being AFK, falling asleep etc. But not even getting them and being kicked is fucking brutal. Whole line up of people on the list here agree I was here, active, and talking at the time even. So it might have some glitches... Maybe it has a hard built time limit? | ||
|
|
|||
![]() |
|
|