Raid Lock *after raid*

[GoogleCodeExporter]

Could I please have more info on the Raid Lock feature?

Seems I'm only able to lock raids "before" it starts.

Not sure why we'd want to lock a raid weeks or months before it starts.

I do not see a feature to lock a raid "after" it's been completed.

If we could lock it (let's say) 1h after the raid.  It would give me time to go 
back to it and add the players that didn't sign up.  (If raid leader is given 
permission to sign others up) or add them as a random.

Original issue reported on code.google.com by try...@gmail.com on 30 May 2013 at 3:36

[GoogleCodeExporter]

The idea of "locking" the raid was implemented to prevent players from 
attending a raid that is due to begin (last minute attends).
We did that to encourage players to sign up as early as possible / to sanction 
players who forget to sign up.
The year/week options are just there because I reuse the methods from the 
"delete raids" field where this makes more sense.

However - the time you set in the "lock raids" field is relative. It's "raid 
start time + time you entered". As of this, just enter a negative number to 
lock the raid after it has been started.

There is a little bug that will convert the number to seconds after saving - 
I'll fix that for 0.9.8a

Original comment by arne.cl...@gmail.com on 30 May 2013 at 1:30

• Changed state: Accepted
• Added labels: FixScheduledFor-0.9.8a

[GoogleCodeExporter]

The attached file will fix the display problem.
Just copy the file to lib/script and overwrite the old one.

Original comment by arne.cl...@gmail.com on 30 May 2013 at 1:35

• Changed state: Done

Attachments:

• settings.js

[GoogleCodeExporter]

Original comment by arne.cl...@gmail.com on 30 May 2013 at 1:45

• Added labels: Found-0.9.8

[GoogleCodeExporter]

Original comment by arne.cl...@gmail.com on 2 Jun 2013 at 11:22

• Changed state: Fixed