SPOILER
http://osu.ppy.sh/forum/60
You are given the option to lock your topic but not to unlock it. BATs however can already do this, why can't we?
As it's already something specifically for mod queues, it'd be great to lock and unlock your topic every time you can mod more beatmaps. open/closed.
This request would solve these problems: t/65133
Would work together with this: t/85389, the person you give your permissions to, could also lock and unlock the thread.
You are given the option to lock your topic but not to unlock it. BATs however can already do this, why can't we?
As it's already something specifically for mod queues, it'd be great to lock and unlock your topic every time you can mod more beatmaps. open/closed.
This request would solve these problems: t/65133
akrolsmir wrote:
Actually, why can't we unlock our own queues yet?
Here's the thread where they requested the ability for you to lock your mod queue: t/30203?hilit=unlockBreeze wrote:
yoshi, I had to say, MATs could not unlock a topic :/
Derekku wrote:
I don't see the harm in this, so... [Added]!
EDIT: Hold that thought... It seems that users wouldn't be able to unlock their threads once locked, and thus this may actually be more trouble than it's worth. Sorry for the false hope.
I'm suggesting a change with an addition to this phpbb, not just an addition and no change to the current system which would cause problems.NoHitter wrote:
Well, people who do ask to BATs to lock their queues more or less also ask them to unlock after a while.
At least with what you did, they only need to ask a BAt to unlock it. (Once vs Twice)
Would work together with this: t/85389, the person you give your permissions to, could also lock and unlock the thread.
I did some research and found out that it isn't easy to implement with this phpbb. I guess it would be better if this request was waiting until osu!web works differently.