AN IMPORTANT UPDATE! PLEASE NOTE

[fairyfoes]

Hey there, fairybros! Some potentially bad news-

It's the holidays and the app team has measured their cumulative time! In past app rounds it has taken weeks to crank through the veritable flood of applications... and unfortunately the app team simply doesn't have enough room on their plates presently to handle the scope of apps generally received in prior sessions. Couple that with the fact that this has been the most-active reserve period the game has yet experienced, and you get a recipe for trouble. While we are aware that reserves are not ironclad commitments to applying, we, nevertheless feel this measure is necessary.

As a result, the decision has been made to enact an application cap of 60.

We regret that this is a necessity, and are deeply apologetic for the short notice and any inconvenience this may cause, but we would rather be dutiful and thorough with less apps than rushed and haphazard with more, especially moving forward. Though the number of the cap may change, after exhaustive discussion, the moderating team is of the opinion that until such a time as the team can be expanded, limiting the amount of applications received will help us manage the game to the quality its current players have come to expect.

Eachdraidh has become a game lush with not just a host of beautifully diverse and extraordinarily executed characters, but the cumulative worldbuilding of its players, the depth and breadth of their experiences. We have worked very diligently to facilitate that, and have tried to place (what we hope is) a strong emphasis on cultivating the manner of player interface with the game to meet player needs and wants. This has resulted in an extraordinary amount of moderator participation in the game, and both the quantity and quality of this participation necessarily wanes the larger the game gets.

Plans are in place for new mechanisms to be released which will help to reduce pressures on the moderating team (and add to their number), and the number of the cap is likely to change in the future in relation to various factors. Getting a reserve in swiftly will not be a confirmation that your app will be counted among the 50 regardless of when it is sent; but that applications will be cut off at the receipt of the 51st. Once again, we apologise for any inconvenience.

Thank you for your support and understanding.

EDIT: In light of things, we're adding an addendum:

New applicants may app up to TWO characters
Players already in the game may app ONE character

Both sets of applicants are being limited, however we believe some priority must be given to potentials. In the event applicants submit more applications than allowed, the app team will ask them to please choose which character(s) they'd like to submit for processing.

ED MODS

Comments

[gloinul]

With this limit, would it be possible to allow people to see which apps are posted? As it stands, we literally have no way of keeping track of the number of applications sent in real time. We have to wait for the list to be updated, and that simply can't be updated as they come in.

[digophelia]

I second this. I don't have plans to bring on another character myself, but I think this would be fair, or at the least have something to let potential appers have a chance to see who is apping. Either way, this sets up a mad dash on the part for you guys, too.

[dragmire]

Thirded, especially since the playerbase will want and should know the order apps come in.

[athousandcurses]

Fourthed, and maybe it would be helpful being given examples of things on other screened posts? Like the quests requests. Going in nobody has any good idea of the parameters available.

[steeledskin]

+1. if the apps are to be capped, then i do believe having apps posted to an entry and left unscreened is the way to go.

[curser]

I agree and disagree. Screening the apps during process is probably the best way to go since with a cap, there's going to be a lot of people keeping an eye on who gets their apps in and if they're 'good enough' to be taking up those spots. I think leaving them unscreened is basically asking for them to be torn apart on places that do that and possibly leading to harassment by people that feel they got their spot stolen.

[steeledskin]

although i recognize the point as a good one (and certainly would hate to see harassment of any kind), i feel like it's important to keep the process as transparent and beyond-reproach as possible. even if it's unlikely any trouble would arise, i think it pre-empts a lot of other nasty accusations if there's an up-front and identifiable way of proving which fifty were the first fifty.

maybe this involves still posting them to an entry and screening them but unscreening them once the process is over. either way, it's the sort of thing that ought to be done out in the open.

[curser]

I think that's a good compromise, especially since we have to have info posts which most people just use to toss up their apps for.

[fairyfoes]

One of the commenters here voiced our largest concern impeccably,

'I think leaving them unscreened is basically asking for them to be torn apart on places that do that and possibly leading to harassment by people that feel they got their spot stolen.'

We can absolutely understand players wanting transparency in the process, however. Would any of you be able to suggest an actionable method for handling this? Ideally one which minimizes need for moderator involvement, perhaps even anonymously self-reported?

[digophelia]

Well, is there a way possibly to indicate the number of the application? Like, for example, application #1 and so forth on the subject line? I know that you guys reply back saying "oh, this has been received" in your application or reserve process.

Now that I can actually understand to avoid any potential bullying people out of the application process.

Actually, I really do like Masa's approach to that.

[dragmire]

If this is a concern (which it should not be to be quite frank), you could have people lock their apps on their journals and grant access to the mod journal after posting. If they are rejected, then only the mods need to know why.

But this is fallible too, because now players are robbed of the chance to know what a quality app was. Was the app for Bob from Popular Canon not as good as Larry from Obscure Canon? Was Bob accepted at Larry's expense so someone 'cool' could get in?

There's no perfect solution to app capping. But I think the smallest sacrifice comes in having apps open, where everyone can see them, and so the process of fairly processing them is seen by all.

[athousandcurses]

I agree with this, especially that it should not be a concern. Other games have app caps and unscreened app posts and don't really have problems with it. People are very familiar with first come, first serve and usually are fairly decent about it, and most people understand the need for caps especially during the holiday season. Honestly I think the extent of it will be "oh damn, I wasn't fast enough!" because the onus is on the player to get the app done and in before the cap is hit, and if they don't there is always next time.

[athousandcurses]

The problem with self reporting is that people may still be reporting they posted an app and the limit will have been reached already as they do not know/can't see how many have been done. Another problem is that they may look at the self reporting, see there's a spot available, go to post, and then come back to report and someone filled it.

[gloinul]

Unfortunately, I'm not sure there's anyway to avoid some level of wank. Leaving them screened will result in people getting pissed that they weren't allowed to apply despite having no way of knowing they were over the limit. Unscreening will (sadly) most likely lead to people being jerks over on the anoncomms and once people get in if they're screened the same thing will happen.

The only way I can think of that would minimize this as much as possible would be to have someone who is able to see the application comments reply with something like "We have received your application" so people can keep track that way. It still leaves a period of lack of updates when people are sleeping, but it's the only thing I can think of.

[(Anonymous)]

The screening/unscreening falls under the same line as the reserves, in my opinion. Especially during the first rush before the list goes up, there's no way to know who got what spot in and who's reserving what, but there are on occasion double reserves. I feel like this falls under the same thing of not knowing if there's a reserve for that char in anyway and tossing it up and hoping for the best. You put your app in and hope like hell you managed to snag a spot.

I do agree that doing a reply would give people more of a gauge of how many spots are available, but tbh, I'm pretty sure that most of the spots will be snagged in the first hour or two. It's the first app cap we've had and I saw how quickly CDC's spots filled up when they had their 50 spot app cap. So this is really going to be a rush of the first few hours.

[gloinul]

Reserves aren't applications, though. Reserves are just saying "I want to play this character". Applications are taking steps to play the character and there is a lot more riding on getting that in as opposed to getting a reserve in. If there's no way to keep track, there will people hating on the mods for it. I mean chances are there's people hating on the mods for this now but a lack of transparency will only make it worse. Even if most of the spots are taken up in the first few hours, people will be pissed if they can't see that for themselves.

[all7seas]

One possible way of doing it is having a lottery with 50 spots even before app-posting time?

NEW SUGGESTION

[fairyfoes]

We can provide append numbers in the apps status list (in order received) as well as the timestamp of receipt alongside the usual character/canon. Applicants can, obviously, confirm their own timestamp, so that in itself should serve as a verification for the validity of their submission.

Yes/no/other?

[gloinul]

It's an idea, but honestly I'm not sure there's a way to do what you guys want to do--make applications less of a hell for your team, and really no one can blame you for wanting to do that--while keeping the applications screened. Doing this will just add more work for you guys to do. I thought about suggesting this myself, but that's a lot of stuff to worry over and I eventually just went with the only idea I could think of that would add the least to your workload since commenting to the screened apps could also eliminate the need to keep a list of received applications (I mean unless people really want to see who all exactly is in waiting).

I really think that if you want to cap applications, you can't screen them. It is the simplest way to make the process transparent and completely eliminates the need for the list of received and processing applications, which is less work for you guys. Yes, there's a chance that people are going to throw a fit over X being considered and not them but there's that chance with any game that has an application cap. There's no way to avoid it, sad as is it.

[(Anonymous)]

I think in lieu of this suggestion and given this statement, yes, that the comments cannot be screened. If a player is concerned about their application being seen, that they can lock it to the moderator accounts only and anything but. It's only fair and that at least gives us players a gauge of how many applications are in.

Furthermore, there's going to be upset people regardless of what comes out of this. It's not going to be easy. But it's important for people to remember you cannot please every anonymous commenter and that do what you can to avoid things that make you upset.

I say let the comments be unscreened as well, lock it to the moderator account if needed for just this one time. But mods, you do a great job with what you've got already and I think Gimli and Ganondorf-mun make excellent points!

[dragmire]

I absolutely agree. And if we're all afraid that someone on wankgate is going to be mad, then... so what?

[fairyfoes]

We apologise, we've read your points and really appreciate the concern, but we have no intention of making applications public and have no plans to reconsider this stance.

We already maintain a processing list so assigning numbers and time stamps wouldn't be much work. We've also discussed leaving unscreened replies along the following when applications are received.

Your application has been received, as of 00:00 GMT! You are the ## applicant for this round.

We believe this provides ample transparency, as applicants will be able to corroborate the time, or contest it should there be an error. If there are mistakes or disputes, we will deal with them accordingly. We wouldn't dream of it, but we wouldn't be able to skip over an applicant who made the cutoff, anyway.

1. Joseph 00:16 GMT
2. Lisa 00:32 GMT
3. Susan 00:48 GMT

For example, Joseph, Lisa, and Susan apply, but only Joseph and Susan receive comments. Lisa can confirm from the list if she believes she has been missed, and bring the matter to our attention.

[scinlae]

i like the sound of that.

[(Anonymous)]

I'm sorry, but that concern is kinda pointless. If someone really wants to wank on the people that got in, they will still do it after they get accepted. We'll find out who those fifty players are the second they make their intro. So why not keep things clear from the beginning?

[(Anonymous)]

Because there's a likelihood, slim though it is, that someone might try to wank someone out of withdrawing their app. Even though the slot will have already been taken, some people are just jerks and like to be mean and spiteful just for the sake of being mean and spiteful. At least if they app and get in, the wank will hopefully just be a spurt that dies down quickly because there's no basis for it.

[(Anonymous)]

I know, my points was: all that can happen after they get accepted too. It wouldn't be the first time someone is wanked out of a game. Like Gimli-mun said, we won't be able to avoid ALL wank. Nobody can, and letting potential wank affect your decisions is a bad idea.

[gordianknots]

How does this cap impact the native OC app, if at all? Or does low volume mean that it is not needed?

[fairyfoes]

It will not affect native OC apps, which are approved by a completely different system!

[gordianknots]

Thank you!

[arms]

There's talk going around that there's one more app round after this one before they close for the timeskip. Is that true? Because some people were planning on apping multiple characters this round, myself included. While I don't feel it would be fair of me to take two slots, so I won't be apping both of my potentials, I had possible plans for characters prior to the timeskip and wanted to see if there would still be a chance to get that app in.

Also asking because it might take some pressure off of others wanting to get apps in, in time for the timeskip, while also opening up space for new blood this round.

[fairyfoes]

You can read all the detailed information on the timeskip here! There will indeed only be one more app cycle before the time skip; however, the app cap will likely be substantially higher during that round (and perhaps may not even exist at all!) because it won't be the holidays, and the moderator team may have grown enough to accommodate lifting the cap.

[arms]

Okay, I thought I saw the information somewhere outside of plurk but just could not remember for the life of me where!

I feel like I've been spending the past week saying thank you to you guys, but I really mean it. Here's hoping that things work out over these next couple months, especially during the trying holiday season - you guys deserve a break as much as anyone else, and the app cap is completely understandable right now.

[(Anonymous)]

Will the mods allow for people to post applications on behalf of others? With high interest and app caps, it seems like that if you are not available until hours after apps open, you may end up completely out of luck. I have seen other games in similar situations allow it but I was wondering what the policy would be here.

Thanks!

[fairyfoes]

We've no problem with this, proxy comment at will. o7

Just ensure the information is correct! We've seen people confuse information or forget, and actually post their own applications instead, in other games.

[playmakings]

The next time you announce this, it would probably be easier for everyone if you announced it sooner? I know a few people who are too busy to canon review until the day apps open; now the likelihood of them even getting in, let alone trying, is low.

[winterwork]

Considering that the sudden attack of a hundred reserves was unexpected, I doubt this was a decision they realized they needed to make until now.

[playmakings]

Ohh--shit, I hadn't thought about that. Wow, go me.

Ignore my comment, mods!

NEW NOTE, please read

[fairyfoes]

*this will be added to the post proper

In light of things, we're adding an addendum:

New applicants may app up to TWO characters
Players already in the game may app ONE character

Both sets of applicants are being limited, however we believe some priority must be given to potentials.

[notavirtue]

The timing sucks and changing more details can get confusing, but just gonna throw it out there. With this being short notice, and apps capped to a more manageable number, would you consider pushing back the date when apps open? I don't know if that's feasible with your timetable or what would even be a good date, though.

[(Anonymous)]

Because of the super late notice on the cap, will the reserves be carried over to the next application round to make it fair to those who had put them in and didn't realise in time?