Long or Short? Application Process!
-
I liked the comic game apps that everybody wrote like Official Handbook entries but I know I’m like the only person who did; they didn’t at all make a difference in the quality of who got approved, and they scared off anybody who wasn’t super hardcore
-
Another factor to consider that I just remembered is that if a player is applying for a role that is of considerable IC power or will have a significant immediate impact on the current plots in the game, a lot of staff (rightly) require a more detailed and lengthy application (and sometimes an interview) to approve the character.
-
At the risk of sounding like I’m victim blaming, we also have to be willing to take “yes” for an answer. If staff explicitly say something like “If your background is more then N words, you’re probably going into more detail than we really need,” and I proceed to write a background that’s 5N words in length … that’s not something staff can fix.
-
Honestly, these days, as far as backgrounds or mechanical explanatory notes or whatever other stuff a game might want… just give me a questionnaire.
-
This post is deleted! -
@Autumn said in Long or Short? Application Process!:
At the risk of sounding like I’m victim blaming, we also have to be willing to take “yes” for an answer. If staff explicitly say something like “If your background is more then N words, you’re probably going into more detail than we really need,” and I proceed to write a background that’s 5N words in length … that’s not something staff can fix.
idk who the victim being blamed in here is — players being blamed for writing more BG than they need? but anyways yeah this is very true and frustrating when it happens. when a game has a maximum word count for BGs, it means that they literally do not need that level of detail and aren’t interested in reading it. i’ve definitely been a part of sending back apps that went over the cap.
-
If I have to apply, I’m already gone.
-
i don’t play games to do homework and, while i have held my nose a few times, it’s not been an experience I’ve found pleasant. A short bit indicating understanding of a roster or theme is one thing, but my characters bloom into life as I play them. Writing a massive backstory that will be retconned into who my character actually ends up being is a waste of time for everyone involved.
-
@Juniper said in Long or Short? Application Process!:
If I have to apply, I’m already gone.
While I understand this and can sometimes agree with it, I’ve also had the experience of playing on games with no application process whatsoever and watched as the game filled up with random trolls and ended up shutting down pretty rapidly.
-
Applications serve exactly one purpose: to make sure you and the character are a good fit for the game. The app process should be as short as functionally possible to meet that purpose. More complex themes will necessarily require a more involved application.
That being said, I absolutely prefer a shorter application process and endorse doing the absolute bare minimum to get an app over the line. GET ON THE GRID and start playing.
If your theme requires all players to spend multiple hours in chargen, you may want to consider whether your theme/mechanics can be streamlined or at least offering premade rosters who don’t require much time to get started with. Applying is not playing, and a long application process usually means more staff work as well, and a nonzero population will apply and then never play. It’s worth making this as painless as you can for everyone involved.
-
@Trashcan said in Long or Short? Application Process!:
That being said, I absolutely prefer a shorter application process and endorse doing the absolute bare minimum to get an app over the line. GET ON THE GRID and start playing.
I agree with this, and in my opinion the bare minimum should be:
- Application Coherency: The application should be coherently readable and make logical sense. I’ve read enough offenses to the written word in my time in the hobby that bad apps will haunt my afterlife.
- Lore Knowledge: The application should indicate that you have a basic understanding of the MU’s setting. Most games these days have a loredump summary type document somewhere that contains all of the information that literally every character in the world would know, and the application should reflect that.
- Mechanical Knowledge: A large majority of MUs have some sort of mechanical system for conflict and task resolution. Some of these are based on TTRPGs with their own published book lines. Your application should reflect that you are familiar with the core mechanics of the game, and possibly note if you are new to the specific system being used. (Being new to a system shouldn’t be cause to deny an app, but should be brought to staff’s attention so that they can help you learn it until you get up to speed.)
There are some optional additions to this as well:
- Acknowledgement of Responsibility: If an application is for a position of IC power or responsibility (and yes I am aware that allowing PCs as IC leaders is often fraught with peril), then the application should include an acknowledgement that said position requires you play your character in a way that generates positive RP experiences for others and not just yourself.
- Roster History Acknowledgement: In games where the application is for a roster character that has already seen play, the player should acknowledge to the staff that they understand the IC storyline already written for their character. If a character has already developed rivals in game, then the character is dropped back to roster and picked up by someone else, their first scene in the game shouldn’t be one where they are suddenly best buddies with those rivals with no logical reason.
