Brand MU Day
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Long or Short? Application Process!

    Scheduled Pinned Locked Moved Rough and Rowdy
    22 Posts 14 Posters 321 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • TrashcanT
      Trashcan
      last edited by

      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.

      he/him
      this machine kills fascists

      MisterBoringM 1 Reply Last reply Reply Quote 3
      • MisterBoringM
        MisterBoring @Trashcan
        last edited by

        @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.

        Proud Member of the Pro-Mummy Alliance

        1 Reply Last reply Reply Quote 0
        • First post
          Last post