Gamemaster Guidelines

Welcome to the Fuse Networks Imperial RP Gamemaster Team!

As a member of the Fuse Networks ImperialRP Gamemaster Team, you will be tasked with creating the events and roleplay experiences our players interact with every day. Your role here is a critical one that ensures community engagement, server growth, and - by extension - our high place within the Garry's Mod server ranks.

The ImperialRP Gamemaster Team provides the Fuse Networks ImperialRP community with creative, entertaining role play, events and simulations.

Our duties include:

• Building creative environments otherwise known as "dupes" in which RP experiences take place.

• Creating the unique and engaging stories that keep players coming back to our community often.

• Assisting battalions with creating realistic combat simulations, fun missions and challenging tryouts.

Rules and Info

Failure to follow these rules and the rules on the other pages of these guidelines can result in punishment.

General Rules

• Never use your ability to spawn NPCs to boost your levels and earn Galactic Credits.

• Follow the rules for your GM rank on the Rank Structure page.

• Do not take staff sits that are not listed as "Need a Gamemaster".

• Limit Roleplay on the ISB job, unless it is absolutely crucial for the current event. You are allowed to come on the ship to transfer information to the highest on - it is then their job to organize the troopers. You do not command them.

• Make sure you are cloaked when in player areas.

• You must always be in Teamspeak "Event Briefing Room" during your events.

• Whenever flying to the ISD on a VTOL make sure it is uncolored and unmaterialized (Senior Gamemaster+ are excused).

• In the Fuse Networks Imperial RP Discord, there is a channel called "#event-suggestions", these ideas are open to all GMs to help make player ideas a reality. If you want to use an idea, make sure to create a thread saying you claim this idea and then conduct the event.

• If you cannot attend a Staff/Gamemaster meeting at 6 PM EST in "Staff Meeting Room-(6PM EST)", put in a meeting excuse in Discord.

• Using headcrab canisters on top of people is NOT allowed. Breaking this rule will be an automatic strike.

• When hosting an event that may involve RP with specific battalions, consider reaching out to Command team for those battalions. Give them a small heads up letting them know what’s happening in your event - and how it will involve their battalion. Generally, it is advised to communicate with Command or High Command in general. This reduces confusion during large and allows for:

  • 1. Cohesive and collaborative events where Command can help run your event as intended

    2. More interaction with key members of the community, which can benefit you as a GM in the long run

    3. More immersive experiences for the players!

Event Rules

Event Player Count Rules

Sometimes, when player count is too high, events can cause server instability. The following player counts may limit event hosting capability:

• At 90+ players:

  • Get permission from SGM+ to do a passive event.

  • Get permission from AHGM or HGM to do a combat event.

  • Get permission from Manager to do an offmap.

• At 95+ players, do not spawn any dupes. NEVER spawn anything that could crash the server.

Claiming Events

Before you host or even announce an event, you must first claim a time slot for it. This ensures that events are pGMs wanting to host an event at a set time can do so, a

• Claim events in the "Event Claiming" channel within the GM section of the Staff Discord. This will ensure you don't interfere with others' claims and event time slots.

• Start your event(s) at the time stated in your claims and pings.

• Delete your claim from the "Event Claiming" channel when the event is over.

• NOTE: Hosting an event during/at someone else's claimed time will lead to a strike.

Event Announcements (AKA Event Pings)

Every event must have an announcement ping, which is posted on the main ImperialRP Discord on the Event Announcements channel. Every event announcement is supposed to read like an advertisement for your event. Through this announcement, the GM is trying to create excitement around the event's story, thereby convincing people to come on the server. From a management standpoint, getting people to engage with the server and come online the is the whole point of pinging and doing events - so this part is fairly crucial in hosting events!

When creating Event Announcements, you must use proper grammar, punctuation, and spelling. Make sure to grab the player's attention with colored text, images, and a strong event description. Finally, you must also specify what type of event you are hosting in an announcement. Be sure to follow the established format in the channel.

Remember - Event Announcements may only be posted 15 minutes before the event is scheduled to begin!

Event Announcements should ALWAYS include:

• Specification of what type of event you are hosting (On-ship/Off-ship/Off-Map, Passive, Combat etc.)

• What is going to happen during the event. It is ok to leave a cliffhanger and not give everything away. The event description should be 3+ sentences.

• An image that illustrates/conveys what the event is about, or a clue of what is to come.

• How long until the event begins (Ex: Starting in 15 minutes). This time should be no longer than 15 minutes ahead of the start of your event. Mega Storylines events can go further - up to 30 minutes ahead of the event.

• How to easily connect to the server.

  • Ex: Use "connect fusenetworks.com" in console to easily connect!

  • Ex: Connect with: steam://connect/199.21.79.143

Event Log and Votes

After hosting an event, you must perform two actions:

1. Cast a vote that allows players to weigh in on how good the event was, and log your event using this form

• For event votes, access the voting menu through the !menu command, adding the following 5 options to the vote:

• • • 1. Great

      2. Good

      3. OK

      4. Poor

      5. Terrible

• Log your event (or side activity) in the official log that is tied to the roster (https://forms.gle/uH2HQFQkUnSUGMdRA).

Event Types

Passive Event

A small event that does not include elements of combat and relies on creative RP. Must take place on the current map. This is the only type of event a TGM can host.

Combat Event

A standard size event that includes elements of combat and storytelling. Combat events can be help on the ship, in an off-ship area like Hoth or Endor, or in an off-map environment. ONLY GM 0+ may host Combat Events, and only GM III+ may host off-map events!

Mega Event

A Mega Event is an event which lasts for over an hour, and uses 2 different /. Must, Must, MUST be planned at least 2 days in advance, on a google doc. Advised to have 2+ GMs working together on a Mega Event. ONLY GM V+ may host Mega Events!

Storyline Event

A Storyline event is the servers main event storyline, the Senior Gamemaster’s are in charge of the Storyline events, but a Regular Gamemaster can also help with it if they are asked. A storyline typically lasts anywhere from 2-3 hours and should be at least 1 map change. Only SGM+ may host Storyline Events!

Side Activity

Side Activities include Simulations, Missions, and Tryouts that assist the battalions onboard ISD-GL. Side Activities are often initiated via a GM Sit - which appears on the server as a "Need a Gamemaster" notice.

Only GM 0+ may accept GM Sits or host Side Activities!

Event Cooldowns

After each type of event, a cooldown is applied before another event can be hosted.

Passive Events - 15 Minute Cooldown

Combat Events - 30 Minute Cooldown

Mega Events - 45 minute Cooldown