Difference between revisions of "Staff:Event"

From MassiveCraft Wiki
Jump to: navigation, search
(Created page with "== Responsibilities == The Event Department is responsible for all sorts of Events on the server and makes a particular effort to make in-game content (quests, events, dungeon...")
 
(Members)
(2 intermediate revisions by the same user not shown)
Line 7: Line 7:
 
To become a staff member we always ask that you post a staff application. You can post an application by following this link towards the [http://forums.massivecraft.com/forums/staff-applications.11/ Staff Application Forums].
 
To become a staff member we always ask that you post a staff application. You can post an application by following this link towards the [http://forums.massivecraft.com/forums/staff-applications.11/ Staff Application Forums].
 
In order to be considered for the Event department, an applicant should have some measure of consistent activity in-game, be organized enough to co-host and plan events, be capable of using Discord Voice for communication during these events, and ideally, have hosted an event or two as a player in the past.  
 
In order to be considered for the Event department, an applicant should have some measure of consistent activity in-game, be organized enough to co-host and plan events, be capable of using Discord Voice for communication during these events, and ideally, have hosted an event or two as a player in the past.  
 +
 +
If an applicant is specifically interested in Quest, they should take the following into consideration. It is not necessary to already know how to write quests before joining the team, but it is recommended that you familiarize yourself with the Quest Workflow and look over the [http://www.massivecraft.com/massivequest-author MassiveQuest Author Commands]. After all, you need to know if this is the right place for you, and it’s wonderful when a new applicant comes prepared with a general understanding of what’s expected. Some go as far as to create a sample quest—just know that it’s not required.
 +
 
== Projects ==
 
== Projects ==
  
Line 24: Line 27:
 
*'''Announcement:''' 1 point.
 
*'''Announcement:''' 1 point.
 
*'''Event Story Writeup:''' 2 points.
 
*'''Event Story Writeup:''' 2 points.
 +
 +
=== Quest Workshop ===
 +
Host a workshop for the Quest department. Workshops can be about teaching people how to write quests or about working together with others to create/implement quests. There should be a well-planned agenda, a set time for the workshop, and a notification given at least three days from when the meeting would begin.
 +
* '''1 point:''' For every hour of productive workshop participation.
 +
* '''+2 points:''' Organizing the workshop.
 +
 +
=== Quest Storyline ===
 +
Write a riveting, creative, and fully developed story that can be converted into a quest for either an existing quest island or the capital city. Do keep in mind that if the story is not interesting, or if no quest writers are interested in the story, you will not be awarded points for it until it is used in a completed quest. The written format for this should follow that found in the Quest Template. This is also available as a Lore project:  http://wiki.massivecraft.com/Staff:Lore#Projects
 +
* '''1 to 2 points:''' For every 15 nodes written, depending on complexity and node quality/length. 
 +
 +
=== Quest Commands===
 +
Turn the storyline into visually formatted commands per the Quest Template. The quest should follow the storyline. Use the commands listed here: http://massivecraft.com/massivequest-author
 +
* '''1 point:''' For every 10 nodes converted.
 +
 +
=== Quest Implementation ===
 +
Implement and debug a quest. You would need to have the commands for the quest you are going to enter. You then need to copy and paste the commands into MassiveCraft. Make sure that you paste them in the order they are listed! Ensure that the nodes all function as expected. This step includes the initial tech quality assurance that should occur prior to bringing in others to test the quest.
 +
* '''1 point:''' For every 10 nodes implemented and debugged to the point where they work as expected.
 +
 +
=== General Quest Quality Assurance ===
 +
Debug and test a quest for quality assurance. Make appropriate fixes as needed and able based upon skill and rank. Refer to the quest document while doing this testing, log your work, and follow the quality assurance checklist.
 +
* '''1 point:''' 1 hour’s worth of productive testing and repair as evaluated by an independent review.
 +
 +
=== Quest Team Integration tasks ===
 +
Resolve items listed by others on the Quest team worksheet. This may include the creation of NPC’s, regions, placing blocks, or otherwise facilitating quest creation.
 +
* '''1 point:''' 1 hour’s worth of productive work assisting the department. Time noted on the sheet will be taken into account but ultimately evaluated on a task by task basis.
  
 
==Members==
 
==Members==
Line 32: Line 60:
 
*Ryria
 
*Ryria
 
*Bellarmina
 
*Bellarmina
*WrongChat
 
  
 
===Members===
 
===Members===
 +
*WrongChat
 
*Derpadillo
 
*Derpadillo
 
*Kniferharm
 
*Kniferharm

Revision as of 21:59, 13 June 2019

Responsibilities

The Event Department is responsible for all sorts of Events on the server and makes a particular effort to make in-game content (quests, events, dungeons, etc) that appeal to all types of players. This Team is designed to be an action group that creates and implements larger scale productions for engagement with the server community, as well as allowing players to request event staff assistance in creating a specialized experience for a group of roleplayers. This team will focus on the development of lore-compliant events in the case of RP and effective minigames in the case of survival.

Conception can come from either players or staff who have an idea for an event. Dedicated staff will build what’s needed to fully immerse our players within the experience. Dungeon Masters and other lore approved characters can also interact with players, as well as to conduct the general flow of the event. In addition, all Rank 2+ will learn the MassiveQuest plugin for integration into events.

Recruitment

To become a staff member we always ask that you post a staff application. You can post an application by following this link towards the Staff Application Forums. In order to be considered for the Event department, an applicant should have some measure of consistent activity in-game, be organized enough to co-host and plan events, be capable of using Discord Voice for communication during these events, and ideally, have hosted an event or two as a player in the past.

If an applicant is specifically interested in Quest, they should take the following into consideration. It is not necessary to already know how to write quests before joining the team, but it is recommended that you familiarize yourself with the Quest Workflow and look over the MassiveQuest Author Commands. After all, you need to know if this is the right place for you, and it’s wonderful when a new applicant comes prepared with a general understanding of what’s expected. Some go as far as to create a sample quest—just know that it’s not required.

Projects

Lore Event

Staff will consult with each other on the feasibility of both the scope of the event, the build, and the timing. These events will not necessarily be limited to a certain amount of roleplayers attending, but rather if the event itself will improve the quality of roleplay, and provide opportunities for character growth, development, and plot progression.

  • Lead/Host on an Event: 5 points.
  • Actor: 2 points.
  • Set up/Builder: 2 points.
  • Announcement: 1 point.
  • Event Story Writeup: 2 points.

Game Event

Game staff will direct the type of event needed to be developed. PvP, chance, or puzzle games that could be enjoyed by the entire server. World staff may assist with the building, quest with functionality, and lore staff with any writing or assistance in story development if needed.

  • Lead/Host on an Event: 5 points.
  • Actor: 2 points.
  • Set up/Builder: 2 points.
  • Announcement: 1 point.
  • Event Story Writeup: 2 points.

Quest Workshop

Host a workshop for the Quest department. Workshops can be about teaching people how to write quests or about working together with others to create/implement quests. There should be a well-planned agenda, a set time for the workshop, and a notification given at least three days from when the meeting would begin.

  • 1 point: For every hour of productive workshop participation.
  • +2 points: Organizing the workshop.

Quest Storyline

Write a riveting, creative, and fully developed story that can be converted into a quest for either an existing quest island or the capital city. Do keep in mind that if the story is not interesting, or if no quest writers are interested in the story, you will not be awarded points for it until it is used in a completed quest. The written format for this should follow that found in the Quest Template. This is also available as a Lore project: http://wiki.massivecraft.com/Staff:Lore#Projects

  • 1 to 2 points: For every 15 nodes written, depending on complexity and node quality/length.

Quest Commands

Turn the storyline into visually formatted commands per the Quest Template. The quest should follow the storyline. Use the commands listed here: http://massivecraft.com/massivequest-author

  • 1 point: For every 10 nodes converted.

Quest Implementation

Implement and debug a quest. You would need to have the commands for the quest you are going to enter. You then need to copy and paste the commands into MassiveCraft. Make sure that you paste them in the order they are listed! Ensure that the nodes all function as expected. This step includes the initial tech quality assurance that should occur prior to bringing in others to test the quest.

  • 1 point: For every 10 nodes implemented and debugged to the point where they work as expected.

General Quest Quality Assurance

Debug and test a quest for quality assurance. Make appropriate fixes as needed and able based upon skill and rank. Refer to the quest document while doing this testing, log your work, and follow the quality assurance checklist.

  • 1 point: 1 hour’s worth of productive testing and repair as evaluated by an independent review.

Quest Team Integration tasks

Resolve items listed by others on the Quest team worksheet. This may include the creation of NPC’s, regions, placing blocks, or otherwise facilitating quest creation.

  • 1 point: 1 hour’s worth of productive work assisting the department. Time noted on the sheet will be taken into account but ultimately evaluated on a task by task basis.

Members

Leaders

  • SpunSugar

Officers

  • Ryria
  • Bellarmina

Members

  • WrongChat
  • Derpadillo
  • Kniferharm
  • SebbySc
  • ZiggyStarDusted
  • Anarchizm
  • OptimalFriskies