As a member of the GamingLight 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 GamingLight 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.
Failure to follow these rules and the rules on the other pages of these guidelines can result in punishment.
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".
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 Gaminglight 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 and allows for:
Cohesive and collaborative events where Command can help run your event as intended
More interaction with key members of the community, which can benefit you as a GM in the long run
More immersive experiences for the players!
Sometimes, when player count is too high, events can cause server instability. The following player counts may limit event hosting capability:
At 90+ players:
No permission needed to do a passive event, but keep props to a minimum.
No permission needed to do a combat event, but do not use drop-pods/NPCs. [Actors Only]
No permission needed to do an off-ship combat, but get dupe checked by a GMV+. [Apply same rules as above]
Get permission from SMT to do an off-map.
At 95+ players:
No permission needed to do a SIM, but no more than 15 props. [One SIM at a time]
Get permission from SGM+ to do a combat event do not use drop-pods/NPCs. [Actors Only]
Get permission from SMT to do an off-ship or an off-map.
Before you host or even announce an event, you must first claim a time slot for it. This ensures that people wanting to host an event at a set time can do so.
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.
You May not claim more than 3 events a day, but if no one else wants to do any event you may claim more. (Don't claim an entire day.)
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!
How to go about writing one
@Event Ping
[On/Off-ship] [Combat/Passive] [MEGA] [Storyline]
"(The name of the event)" < name of event
(My example of what to write)
Reports are coming in that a very serious and dangerous groups of mercenaries have been tasked with taking two of our finest naval, reports don't say who they are, but the ISD-GL has been the one targeted. All troopers to battle stations and protect the ISD-GL and her finest from this daring attack, repel them back to where they came. best of luck to the troopers of the ISD-GL. < this part should be at least 3 lines with detail of what will happen or close to what will happen.
ISD-GL will see the enemy in the next 15 Minutes! <time should be 15 min for combat events and 5/10 for passives.
Connect With: steam://connect/205.178.177.12:27015 or put "connect imperialrp.gaminglight.com" in console * <make sure to include this.
Event Announcements (Sims/Missions)
Remember - This isn't like an Event but more or less for Public Missions and or SIMs. 10 Minute Cooldowns for every Ping.
Mission Ping
__**[Host: | GM: ]**__
__** *[Mission]* **__
`(description of the Mission, just like an Event but a little less Detail as it's a small Mission.)`
__**{What reward that's being given out, mainly for Promotions, but if you have nothing just put N/A}**__
__**Join the Public Mission now by clicking on the Steam Connect Link!!**__
Connect With: steam://connect/205.178.177.12:27015 or put "connect imperialrp.gaminglight.com" in console!
Connect With: steam://connect/205.178.177.12:27015 or put "connect imperialrp.gaminglight.com" in console!
Connect With: steam://connect/205.178.177.12:27015 or put "connect imperialrp.gaminglight.com" in console!
There will be a Custom Banner for the Ping - https://media.discordapp.net/attachments/858515553064452126/1009630001668292638/unknown.png?width=961&height=243
SIM Ping
__**[Host: | GM: ]**__
__** *[ Type of SIM]* **__
`(description of the SIM, doesn't need to be a lot but enough to give the player the Idea)`
__**{What reward that's being given out, if nothing just put N/A}**__
__**Join the Simulation now by clicking on the Steam Connect Link!!**__
Connect With: steam://connect/205.178.177.12:27015 or put "connect imperialrp.gaminglight.com" in console!
Connect With: steam://connect/205.178.177.12:27015 or put "connect imperialrp.gaminglight.com" in console!
Connect With: steam://connect/205.178.177.12:27015 or put "connect imperialrp.gaminglight.com" in console!
There will be a Custom Banner for the Ping - https://media.discordapp.net/attachments/858515553064452126/1009630029648498839/unknown.png?width=1024&height=181
Do remember that a 10 minute ping cooldown is announced after every ping, Failure to follow that will result in a Punishment.
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 imperialrp.gaminglight.com" in console to easily connect!
Ex: Connect with: steam://connect/205.178.177.12:27015
Event Log and Votes
After hosting an event, you must perform two actions:
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:
Great
Good
OK
Poor
Terrible
Log your event (or side activity) in the official log that is tied to the roster (Event and Side Activity Log).
A small event that does not include elements of combat and relies on creative RP. Must take place on the current map. Passive Events count as 1/2 of an event!! Meaning you must do 2 passive events to count as one full 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. All GM's may host Combat once trained!! But only GM III+ may host off-map events with approval from Head GM Overseer.
A Mega Event is an event which lasts for over an hour, and uses 2 different areas. 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! GMIII and GM IV may host a mega with permission from SGM+ and must have a GMV+ CoHosting and watching over it.
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 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.
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