Gamemaster Information - Revision history

PursuitinAshes: Remove Commands to be placed on discord instead

2026-03-30T15:35:29Z

Remove Commands to be placed on discord instead

← Older revision		Revision as of 15:35, 30 March 2026
Line 95:		Line 95:
	* A guide to [https://docs.google.com/document/d/1Y1kYisWqhHLBX5E9auwqLKDONKIOQeGgYVnzpN-qKAI/edit?usp=sharing writing and running your first script], including some basic commands and expectations. While primarily for Trial GMs, there is possibly helpful information in this document.		* A guide to [https://docs.google.com/document/d/1Y1kYisWqhHLBX5E9auwqLKDONKIOQeGgYVnzpN-qKAI/edit?usp=sharing writing and running your first script], including some basic commands and expectations. While primarily for Trial GMs, there is possibly helpful information in this document.
	* The [https://docs.google.com/document/d/1xl95isvLp8DPnGGFngDVYZySJohOVZNSffexcISHuDI/edit?usp=sharing PVE Player Guide], which includes valuable information for first time players. This should be attached to round announcements.		* The [https://docs.google.com/document/d/1xl95isvLp8DPnGGFngDVYZySJohOVZNSffexcISHuDI/edit?usp=sharing PVE Player Guide], which includes valuable information for first time players. This should be attached to round announcements.

	~~== Command List ==~~

	* '''uploadfile /<filename>.ogg''' - Uploads a sound file to the server, under the name you specify. (Opens your file explorer to actually select which file to be uploaded)
	* '''playglobalsound /uploaded/<filename>.ogg 4''' - Plays an uploaded sound globally. 4 is an interchangeable volume variable, with 4 being loud enough to hear above standard SS14 ambient tracks in most cases.
	* '''aresannounce <Message>''' - Sends an announcement by’Ares V3.2’
	* ('''setooc, setlooc, setdchat''') - Toggles on and off access for non-admins to speak in the respective chat.
	* '''weather <MapId> <WeatherPrototype> <Duration>''' - Sets the weather on the specified map. Duration is optional. WeatherPrototype should automatically fill with options.
	* '''marineannounce <Sender> <Message>''' - Sends a marine announcement from the specified sender.
	* '''> hive:alldefault''' - Sets all ‘rouge’ (Admin Spawned) xeno entities (Structures and Xenos themselves) to the default hive.
	* '''Fixpower''' - Fixes power on the map you are currently on. Forces power to be ‘on’.
	* '''Loadplanetmap <mappath>''' - Loads a planetmap with the ‘RMCPlanet’ and ‘Tactical Map’ components automatically attached. Runs fixpower automatically.
	* '''Rmcannounce:xenopopuptomarines <Message>''' - Sends a popup from ‘????’, plays the xeno bioscan sounds. <sub>(Disclaimer, below are commands that require full gamemaster perms.</sub>

	~~===== SGM Perms are required to be able to run the below commands; =====~~
	* '''Showmarkers''' - When active shows hidden markers (IE: Spawns, LZ Destinations, Tactical Map Markers, etc.)
	* '''self nearby <#OfTiles> with Ghost select <#OfGhosts> spawnhereasjob <JobPrototype>''' - Spawns #OfGhosts, chosen from #OfTiles from you, as JobProtoype.
	* '''Roundend:settext''' - Command to manually set the end of round text displayed on the end of round screen. Can also be set through the Gamemaster UI.
	* '''> ent <id> icon:set “<icon_state>”''' - ''' '''Changes an entities’ icon if they have the Marine component. Icon_State must come from a file in `Textures/_RMC14/Interface/cm_job_icons.rsi`
	* '''vvwrite /entity/[id]/Rank/Rank <rankprototype>''' - Changes the target id’s rank. Currently doesn’t autofill so get rank prototypes from the code.
	* '''> stations:get jobs:job <job> jobs:adjust <amount>''' - Adjusts the amount of jobslots for the specified role. (In place of ‘adjust’ there is also; ‘isinfinite’, ‘set’, ‘amount’). Currently doesn’t autofill, so get job prototypes from the code.
	* '''> stations:get jobs:jobs jobs:set 0''' - Will set all latejoinable jobs (The ones that display in the spawn menu) to be closed and inaccessible.

Whisper: /* Round Running Policies */

2026-03-08T20:31:06Z

Round Running Policies

← Older revision		Revision as of 20:31, 8 March 2026
Line 64:		Line 64:
	=== New Round Submission, All Positions ===		=== New Round Submission, All Positions ===
	* The ‘#round-organizing’ forum should be used to submit your scripts.		* The ‘#round-organizing’ forum should be used to submit your scripts.
	* All rounds require a script to ensure round quality. It should outline the opening, general gameplay expected, and potential outcomes to prepare for, as well as any information that should be included per the round organizing general guide- such as the opening primer to be posted.		* All rounds require a script to ensure round quality. It should outline the opening, general gameplay expected, and potential ending outcomes to prepare for, as well as any information that should be included per the round organizing general guide- such as the opening primer to be posted.
	** The point of this is to ensure players understand what is happening in the round, and for PvE GMs to easily review the round, rerun it, and ensure that the round has a proper flow and quality standard.		** The point of this is to ensure players understand what is happening in the round, and for PvE GMs to easily review and assist in the round, rerun it, and ensure that the round has a proper flow and a quality standard.
	* All rounds, no matter how simple, must be submitted in a post in this forum, with the exception of Whiskey Outpost rounds and reruns.		* All rounds, no matter how simple, must be submitted in a post in this forum, with the exception of Whiskey Outpost rounds and reruns.

Whisper: /* New Round Submission, All Positions */

2026-03-08T20:16:04Z

New Round Submission, All Positions

← Older revision		Revision as of 20:16, 8 March 2026
Line 63:		Line 63:

	=== New Round Submission, All Positions ===		=== New Round Submission, All Positions ===
	* The ‘#round-organizing’ forum should be used ~~when you have become~~ a ~~member~~ of the ~~GM team~~ to ~~submit your scripts~~. If you are a junior, ~~they~~ will go through a similar process to your initial ticket. Be certain to label your post at least with ‘Yet to be run’ for ease of review as required.		* The ‘#round-organizing’ forum should be used to submit your scripts.
			* All rounds require a script to ensure round quality. It should outline the opening, general gameplay expected, and potential outcomes to prepare for, as well as any information that should be included per the round organizing general guide- such as the opening primer to be posted.
			** The point of this is to ensure players understand what is happening in the round, and for PvE GMs to easily review the round, rerun it, and ensure that the round has a proper flow and quality standard.
			* All rounds, no matter how simple, must be submitted in a post in this forum, with the exception of Whiskey Outpost rounds and reruns.

			==== Jr GM Rounds ====

			* If you are a junior, you will go through a similar process to your initial trial ticket. Be certain to label your post at least with ‘Yet to be run’ for ease of review as required.

	* As a Jr. GM, the person who approves your round does not necessarily have to be the Supervising GM for the round. However, if it is a different member of the team, ensure that they are well informed about your intent and contents of your script.		* As a Jr. GM, the person who approves your round does not necessarily have to be the Supervising GM for the round. However, if it is a different member of the team, ensure that they are well informed about your intent and contents of your script.
	* Even for short scripts, still post them in the form of a google doc. All rounds, no matter how simple, must be submitted in a post in this forum, with the exception of Whiskey Outpost rounds.

	=== Handling Trial GM Rounds ===		=== Handling Trial GM Rounds ===

Whisper: /* Handling Jr. GM Rounds and Promotion */

2026-03-01T23:22:13Z

Handling Jr. GM Rounds and Promotion

← Older revision		Revision as of 23:22, 1 March 2026
Line 79:		Line 79:
	=== Handling Jr. GM Rounds and Promotion ===		=== Handling Jr. GM Rounds and Promotion ===
	Most procedure from the [[Mentoring new whitelist holders]] page should be followed, with a few additions and changes overriding, where any Senior gamemaster can be considered a "mentor" if they choose to do so.		Most procedure from the [[Mentoring new whitelist holders]] page should be followed, with a few additions and changes overriding, where any Senior gamemaster can be considered a "mentor" if they choose to do so.
	* All rounds ran by a Jr. GM will be reviewed in a single private review thread (Locked to just those with the SGM Discord Role ~~& Whisper~~) in the ~~Senior~~ GM ~~chat.~~ The purpose of this is to discuss both the good and bad of the round in more detail and track the progress of each Jr. GM. The end goal of ~~these threads~~ should be to gather information to pass on to the Jr. GM of what went well and poorly~~. Be certain to be able to present this information in a positive manner~~. The first message in this thread should include some basic information about the round and the message link to the round organizing post for it.		* All rounds ran by a Jr. GM will be reviewed in a single private review thread (Locked to just those with the SGM Discord Role) in the '''SENIOR-PVE-GM''' channel The purpose of this is to discuss both the good and bad of the round in more detail and track the progress of each Jr. GM. The end goal of this thread should be to gather information to pass on to the Jr. GM of what went well and poorly. The first message in this thread should include some basic information about the round and the message link to the round organizing post for it.
			* A single thread for all rounds, between the Seniors and the Junior should be made for contact in the '''PVE-GM''' channel. Be certain to be able to present this information in a positive manner.
	* After rounds ran by a Jr. GM conclude, the Supervising GM should discuss the round with them. This discussion should include what went well, poorly, things that could be improved upon if the round was to be rerun, and so on. Do not just focus on the negative of the round where possible, discussing what went well is just as beneficial for all involved.		* After rounds ran by a Jr. GM conclude, the Supervising GM should discuss the round with them. This discussion should include what went well, poorly, things that could be improved upon if the round was to be rerun, and so on. Do not just focus on the negative of the round where possible, discussing what went well is just as beneficial for all involved.
	* After either 3 rounds or a month of being a JGM, the GM responsible for their mentoring should mention in their thread about their promotion, wherein it will be decided if they are ready and meet the standards of a Senior, or if they must perform in 3 more rounds / another month for another review.		* After either 3 rounds or a month of being a JGM, the GM responsible for their mentoring should mention in their thread about their promotion, wherein it will be decided if they are ready and meet the standards of a Senior, or if they must perform in 3 more rounds / another month for another review.

Whisper: /* Handling Jr. GM Rounds and Promotion */

2026-02-14T20:35:45Z

Handling Jr. GM Rounds and Promotion

← Older revision		Revision as of 20:35, 14 February 2026
Line 81:		Line 81:
	* All rounds ran by a Jr. GM will be reviewed in a single private review thread (Locked to just those with the SGM Discord Role & Whisper) in the Senior GM chat. The purpose of this is to discuss both the good and bad of the round in more detail and track the progress of each Jr. GM. The end goal of these threads should be to gather information to pass on to the Jr. GM of what went well and poorly. Be certain to be able to present this information in a positive manner. The first message in this thread should include some basic information about the round and the message link to the round organizing post for it.		* All rounds ran by a Jr. GM will be reviewed in a single private review thread (Locked to just those with the SGM Discord Role & Whisper) in the Senior GM chat. The purpose of this is to discuss both the good and bad of the round in more detail and track the progress of each Jr. GM. The end goal of these threads should be to gather information to pass on to the Jr. GM of what went well and poorly. Be certain to be able to present this information in a positive manner. The first message in this thread should include some basic information about the round and the message link to the round organizing post for it.
	* After rounds ran by a Jr. GM conclude, the Supervising GM should discuss the round with them. This discussion should include what went well, poorly, things that could be improved upon if the round was to be rerun, and so on. Do not just focus on the negative of the round where possible, discussing what went well is just as beneficial for all involved.		* After rounds ran by a Jr. GM conclude, the Supervising GM should discuss the round with them. This discussion should include what went well, poorly, things that could be improved upon if the round was to be rerun, and so on. Do not just focus on the negative of the round where possible, discussing what went well is just as beneficial for all involved.
	* After either 3 rounds or a month of being a JGM, the GM responsible for their mentoring should ~~start a~~ thread ~~regarding~~ their promotion, wherein it will be decided if they are ready and meet the standards of a Senior, or if they must perform in 3 more rounds / another month for another review.		* After either 3 rounds or a month of being a JGM, the GM responsible for their mentoring should mention in their thread about their promotion, wherein it will be decided if they are ready and meet the standards of a Senior, or if they must perform in 3 more rounds / another month for another review.

	== Resources ==		== Resources ==

Whisper: /* General Policies */

2026-01-22T01:03:46Z

General Policies

← Older revision		Revision as of 01:03, 22 January 2026
Line 28:		Line 28:
	* '''Re-run''' - Hosting a previously ran and approved session again.		* '''Re-run''' - Hosting a previously ran and approved session again.

	== General ~~Policies~~ ==		== Policies ==

			=== General ===
			* Gamemasters and Admins alike should refrain from issuing medals on the Normandy server as they will carry over to the Alamo.
			* Do not use your admin permissions on the Alamo server in any form.

			=== Community Behavior ===

	* Upkeep a positive reputation in the overall community, meaning both in-game and out.		* Upkeep a positive reputation in the overall community, meaning both in-game and out.
	* Maintain kind, respectful, and positive behavior both in-game and out.		* Maintain kind, respectful, and positive behavior both in-game and out.
	* PII and Other Sensitive Information (Ex: Knowledge about admin action in a round, tickets, etc.) must be delicately handled by '''all''' members of the GM team, but especially Senior Gamemasters. Do not discuss or share PII (And Other Sensitive Information) outside of the Senior Gamemaster Chat.		* PII and Other Sensitive Information (Ex: Knowledge about admin action in a round, tickets, etc.) must be delicately handled by '''all''' members of the GM team, but especially Senior Gamemasters. Do not discuss or share PII (And Other Sensitive Information) outside of the Senior Gamemaster Chat.
	* Pings for individual rounds should be kept to only two pings~~; One for the primer, round information, start time, etc. One for notifying that the server is open to standard connections~~. Anything else (Ex: Votes for potential scripts or round modifiers, etc) should not be pinged out for but may still be posted in the announcement channel. The message containing the primer must also include the server's IP and a link to the PvE player guide. If the round is being lead by a Jr. GM or Trial GM it must also specify who the Lead GM and Supervising GM are.
	* ~~Gamemasters and Admins alike should refrain from issuing medals on~~ the ~~Normandy~~ server ~~as they will carry over~~ to ~~the Alamo~~.		=== Pings ===
	* Both the Lead GM and Supervising GM, at minimum, must be present (Even if muted, speaking through text is entirely fine) in the PVE GM voice channel when running a round. This is to allow for easy access and communication if required.		Pings for individual rounds should be kept to only two pings. Anything else (Ex: Votes for potential scripts or round modifiers, etc) should not be pinged out for but may still be posted in the announcement channel. The message containing the primer must also include the server's IP and a link to the PvE player guide. If the round is being lead by a Jr. GM or Trial GM it must also specify who the Lead GM and Supervising GM are.
	* Do not ~~use your admin permissions on~~ the ~~Alamo server~~ in ~~any form~~.
			* One for the primer, round information, start time, etc, trying for a minimum of 1 hour earlier;
			* The second for notifying that the server is open to standard connections.

			=== Voice Chat ===
			Both the Lead GM and Supervising GM, at minimum, must be present (Even if muted, speaking through text is entirely fine) in the PVE GM voice channel when running a round. This is to allow for easy access and communication if required. Do not remain in VC when given a role unless explicit permission is given by the supervising GM present. You are free to ask for permission, which can be granted in the case of roles where it is crucial to have a direct line of communication to the lead GM and/or by the judgement of the supervising GM.

	=== Handling Problematic Players ===		=== Handling Problematic Players ===
Line 47:		Line 58:

	=== Remaining in Admin In-Round ===		=== Remaining in Admin In-Round ===
			Generally speaking, once you have received a role or prop in a round, use of de-admin is expected as normal. In situations where direct access to tools like admin chat is required by the player anyways (For things like round flow or reducing Gamemaster workload), the Supervising GM can grant permission to remain an admin while playing in the round. This permission must be explicitly given on a case by case basis.

	* Generally speaking, once you have received a role or prop in a round, use of de-admin is expected as normal. In situations where direct access to tools like admin chat is required by the player anyways (For things like round flow or reducing Gamemaster workload), the Supervising GM can grant permission to remain an admin while playing in the round. This permission must be explicitly given on a case by case basis.		= Round Running Policies =

	~~=== VC =~~==

	* Do not remain in VC when given a role unless explicit permission is given by the supervising GM present. You are free to ask for permission, which can be granted in the case of roles where it is crucial to have a direct line of communication to the lead GM and/or by the judgement of the supervising GM.		=== New Round Submission, All Positions ===

	~~= Other Policies~~ =
	== New Round Submission ==
	* The ‘#round-organizing’ forum should be used when you have become a member of the GM team to submit your scripts. If you are a junior, they will go through a similar process to your initial ticket. Be certain to label your post at least with ‘Yet to be run’ for ease of review as required.		* The ‘#round-organizing’ forum should be used when you have become a member of the GM team to submit your scripts. If you are a junior, they will go through a similar process to your initial ticket. Be certain to label your post at least with ‘Yet to be run’ for ease of review as required.
			* As a Jr. GM, the person who approves your round does not necessarily have to be the Supervising GM for the round. However, if it is a different member of the team, ensure that they are well informed about your intent and contents of your script.
	* Even for short scripts, still post them in the form of a google doc. All rounds, no matter how simple, must be submitted in a post in this forum, with the exception of Whiskey Outpost rounds.		* Even for short scripts, still post them in the form of a google doc. All rounds, no matter how simple, must be submitted in a post in this forum, with the exception of Whiskey Outpost rounds.
	* As a Jr. GM, the person who approves your round does not necessarily have to be the Supervising GM for the round. However, if it is a different member of the team, ensure that they are well informed about your intent and contents of your script.

	~~== Handling Trial GM Rounds ==~~

			=== Handling Trial GM Rounds ===
	# Script approved by SGMs after review.		# Script approved by SGMs after review.
	# Host(s) notified 48 hours (Minimum) in advance to provide permissions required.		# Host(s) notified 48 hours (Minimum) in advance to provide permissions required.
	# SGM and Trial GM join the pve-gm voice chat half an hour in advance to the server being open to connections in order to discuss GM/Admin tools and anything else required for the specific round.		# SGM and Trial GM join the pve-gm voice chat half an hour in advance to the server being open to connections in order to discuss GM/Admin tools and anything else required for the specific round.
	# Post round; review thread made internally with the SGMs to discuss if the user should become a junior GM. Mandatory 48 hour discussion period on the user/round, to be extended as required.		# Post round; review thread made internally with the SGMs to discuss if the user should become a junior GM. Mandatory 48 hour discussion period on the user/round, to be extended as required.
	## After notifying the hosts for permission updates, this will result in either:		#* After notifying the hosts for permission updates, this will result in either:
	### The person being removed from trial and directed they should try participating in more PvE rounds for experience, and they may try again (a time period should be provided, anywhere from 3 months or more.)		#** The person being removed from trial and directed they should try participating in more PvE rounds for experience, and they may try again (a time period should be provided, anywhere from 3 months or more.)
	### The person becomes a JGM.		#** The person becomes a JGM.
	# Trial GM is notified of SGM decision once consensus is made.		# Trial GM is notified of SGM decision once consensus is made.

	== Jr. GM Rounds and Promotion ==		=== Handling Jr. GM Rounds and Promotion ===
	Most procedure from the [[Mentoring new whitelist holders]] page should be followed, with a few additions and changes overriding, where any Senior gamemaster can be considered a "mentor" if they choose to do so.		Most procedure from the [[Mentoring new whitelist holders]] page should be followed, with a few additions and changes overriding, where any Senior gamemaster can be considered a "mentor" if they choose to do so.
	* All rounds ran by a Jr. GM will be reviewed in a single private review thread (Locked to just those with the SGM Discord Role & Whisper) in the Senior GM chat. The purpose of this is to discuss both the good and bad of the round in more detail and track the progress of each Jr. GM. The end goal of these threads should be to gather information to pass on to the Jr. GM of what went well and poorly. Be certain to be able to present this information in a positive manner. The first message in this thread should include some basic information about the round and the message link to the round organizing post for it.		* All rounds ran by a Jr. GM will be reviewed in a single private review thread (Locked to just those with the SGM Discord Role & Whisper) in the Senior GM chat. The purpose of this is to discuss both the good and bad of the round in more detail and track the progress of each Jr. GM. The end goal of these threads should be to gather information to pass on to the Jr. GM of what went well and poorly. Be certain to be able to present this information in a positive manner. The first message in this thread should include some basic information about the round and the message link to the round organizing post for it.

Whisper: /* Round Information */

2026-01-18T20:37:31Z

Round Information

← Older revision		Revision as of 20:37, 18 January 2026
Line 15:		Line 15:
	* '''Primer''' - A string of text which is posted as an announcement / “brief” for a session, giving some lore or detailing into what might occur. GMs must disclose any non-standard ‘tags’ related to their round. (Ex: A greenshift, a first contact, a meme operation, large amounts of HvH etc.)		* '''Primer''' - A string of text which is posted as an announcement / “brief” for a session, giving some lore or detailing into what might occur. GMs must disclose any non-standard ‘tags’ related to their round. (Ex: A greenshift, a first contact, a meme operation, large amounts of HvH etc.)
	* '''HVH''' - Human vs Human		* '''HVH''' - Human vs Human
	* '''Xai''' - ~~Xeno~~ AI		* '''Xai''' - Xenonid AI
	* '''Hai''' - Human AI		* '''Hai''' - Human AI
	* '''~~Meme~~ Operations''' - Self explanatory, anything that is ~~meme-y / joke-y~~ in nature. This is ~~different from~~ an operation with a silly concept - An operation where a group of pizza delivery drivers are sucked into a xeno infested hive is not the same as an operation where you’re space wizards fighting interdimensional crows, monkeys with laser swords, and goblins that crawl in the walls.
			=== Round Types ===
			* '''Non-standard (formerly called meme) Operations''' - Self explanatory, anything that is less serious in nature. This is does not mean an operation with a silly concept - An operation where a group of pizza delivery drivers are sucked into a xeno infested hive is not the same as an operation where you’re space wizards fighting interdimensional crows, monkeys with laser swords, and goblins that crawl in the walls. Make sure these are still grounded within reason.
	* '''First Contact''' - Primary faction is unaware of what they will be facing groundside. (Ex: Unaware of any information regarding xenos, their abilities, or life cycles.)		* '''First Contact''' - Primary faction is unaware of what they will be facing groundside. (Ex: Unaware of any information regarding xenos, their abilities, or life cycles.)
	* '''Slowburn Operations''' - An operation that has a large period of buildup and prior to action, with said buildup taking up more than half of the operation’s expected time before combat.		* '''Slowburn Operations''' - An operation that has a large period of buildup and prior to action, with said buildup taking up more than half of the operation’s expected time before combat.
Line 48:		Line 50:
	* Generally speaking, once you have received a role or prop in a round, use of de-admin is expected as normal. In situations where direct access to tools like admin chat is required by the player anyways (For things like round flow or reducing Gamemaster workload), the Supervising GM can grant permission to remain an admin while playing in the round. This permission must be explicitly given on a case by case basis.		* Generally speaking, once you have received a role or prop in a round, use of de-admin is expected as normal. In situations where direct access to tools like admin chat is required by the player anyways (For things like round flow or reducing Gamemaster workload), the Supervising GM can grant permission to remain an admin while playing in the round. This permission must be explicitly given on a case by case basis.

	=== VC ~~Policy~~ ===		=== VC ===

	* Do not remain in VC when given a role unless explicit permission is given by the supervising GM present. You are free to ask for permission, which can be granted in the case of roles where it is crucial to have a direct line of communication to the lead GM and/or by the judgement of the supervising GM.		* Do not remain in VC when given a role unless explicit permission is given by the supervising GM present. You are free to ask for permission, which can be granted in the case of roles where it is crucial to have a direct line of communication to the lead GM and/or by the judgement of the supervising GM.

	= Other Policies =		= Other Policies =
	== Round Submission ~~Procedure~~ ==		== New Round Submission ==
	* The ‘#round-organizing’ forum ~~is for~~ when you have become a member of the GM team to submit your scripts ~~and have them~~ go through a similar process to your initial ticket. Be certain to label your post at least with ‘Yet to be run’ for ease of review as required.		* The ‘#round-organizing’ forum should be used when you have become a member of the GM team to submit your scripts. If you are a junior, they will go through a similar process to your initial ticket. Be certain to label your post at least with ‘Yet to be run’ for ease of review as required.
	* Even for short scripts, still post them in the form of a google doc. All rounds, no matter how simple, must be submitted in a post in this forum, with the exception of Whiskey Outpost rounds.		* Even for short scripts, still post them in the form of a google doc. All rounds, no matter how simple, must be submitted in a post in this forum, with the exception of Whiskey Outpost rounds.
	* As a Jr. GM, the person who approves your round does not necessarily have to be the Supervising GM for the round. However, if it is a different member of the team, ensure that they are well informed about your intent and contents of your script.		* As a Jr. GM, the person who approves your round does not necessarily have to be the Supervising GM for the round. However, if it is a different member of the team, ensure that they are well informed about your intent and contents of your script.

	== Trial GM Rounds ==		== Handling Trial GM Rounds ==

	# Script approved by SGMs after review.		# Script approved by SGMs after review.
	# Host(s) notified 48 hours (Minimum) in advance to provide permissions required.		# Host(s) notified 48 hours (Minimum) in advance to provide permissions required.
	# SGM and Trial GM join the pve-gm voice chat half an hour in advance to the server being open to connections in order to discuss GM/Admin tools and anything else required for the specific round.		# SGM and Trial GM join the pve-gm voice chat half an hour in advance to the server being open to connections in order to discuss GM/Admin tools and anything else required for the specific round.
	# Post round; review thread made internally with the SGMs to discuss if the user should ~~stay~~. Mandatory 48 hour discussion period on the user/round, to be extended as required.		# Post round; review thread made internally with the SGMs to discuss if the user should become a junior GM. Mandatory 48 hour discussion period on the user/round, to be extended as required.
	# Trial GM is notified of SGM decision ~~to remain~~ once consensus is made.		## After notifying the hosts for permission updates, this will result in either:
			### The person being removed from trial and directed they should try participating in more PvE rounds for experience, and they may try again (a time period should be provided, anywhere from 3 months or more.)
	~~== Jr. GM Rounds ==~~		### The person becomes a JGM.
			# Trial GM is notified of SGM decision once consensus is made.

	* All rounds ran by a Jr. GM will ~~receive~~ a private review thread (Locked to just those with the SGM Discord Role & Whisper) in the Senior GM chat. The purpose of this is to discuss both the good and bad of the round in more detail and track the progress of each Jr. GM. The end goal of these threads should be to gather information to pass on to the Jr. GM of what went well and poorly. Be certain to be able to present this information in a positive manner. The first message in this thread should include some basic information about the round and the message link to the round organizing post for it.		== Jr. GM Rounds and Promotion ==
			Most procedure from the [[Mentoring new whitelist holders]] page should be followed, with a few additions and changes overriding, where any Senior gamemaster can be considered a "mentor" if they choose to do so.
			* All rounds ran by a Jr. GM will be reviewed in a single private review thread (Locked to just those with the SGM Discord Role & Whisper) in the Senior GM chat. The purpose of this is to discuss both the good and bad of the round in more detail and track the progress of each Jr. GM. The end goal of these threads should be to gather information to pass on to the Jr. GM of what went well and poorly. Be certain to be able to present this information in a positive manner. The first message in this thread should include some basic information about the round and the message link to the round organizing post for it.
	* After rounds ran by a Jr. GM conclude, the Supervising GM should discuss the round with them. This discussion should include what went well, poorly, things that could be improved upon if the round was to be rerun, and so on. Do not just focus on the negative of the round where possible, discussing what went well is just as beneficial for all involved.		* After rounds ran by a Jr. GM conclude, the Supervising GM should discuss the round with them. This discussion should include what went well, poorly, things that could be improved upon if the round was to be rerun, and so on. Do not just focus on the negative of the round where possible, discussing what went well is just as beneficial for all involved.
	* ~~When~~ a ~~Senior Gamemaster feels as if~~ a ~~Jr. Gamemaster is ready~~ for ~~possible~~ promotion, they ~~may bring~~ the ~~discussion up to the other senior members~~ in ~~a private thread. The starting thread message should include a list of their previously ran~~ rounds ~~(Pulled from the #round-organizing forum)~~.		* After either 3 rounds or a month of being a JGM, the GM responsible for their mentoring should start a thread regarding their promotion, wherein it will be decided if they are ready and meet the standards of a Senior, or if they must perform in 3 more rounds / another month for another review.

	== Resources ==		== Resources ==

Whisper: /* Upcoming Gamemaster/Admin Tools */

2026-01-18T07:01:38Z

Upcoming Gamemaster/Admin Tools

← Older revision		Revision as of 07:01, 18 January 2026
Line 1:		Line 1:
	~~== Introduction ==~~
	This page outlines the key responsibilities, policies, and expectations for all members of the Gamemaster team. It contains both policies and notes/resources intended to be useful for all members of the GM team at varying levels of skill and ability.		This page outlines the key responsibilities, policies, and expectations for all members of the Gamemaster team. It contains both policies and notes/resources intended to be useful for all members of the GM team at varying levels of skill and ability.

Line 45:		Line 44:
	As for roles that will be whitelisted in the future but are not currently whitelisted (IE: Synthetics and Preds); the hosts have asked that we avoid spawning them outright unless absolutely required. These roles are unfinished and unpolished, so they should be avoided. If a role is absolutely required, it must be someone highly trusted and knowledgeable about that role (Like a game admin or whitelist holder). Avoid writing scripts that entirely hinge around the presence of these roles.		As for roles that will be whitelisted in the future but are not currently whitelisted (IE: Synthetics and Preds); the hosts have asked that we avoid spawning them outright unless absolutely required. These roles are unfinished and unpolished, so they should be avoided. If a role is absolutely required, it must be someone highly trusted and knowledgeable about that role (Like a game admin or whitelist holder). Avoid writing scripts that entirely hinge around the presence of these roles.

	== ~~SGM Policies~~ ==		=== Remaining in Admin In-Round ===

	*		* Generally speaking, once you have received a role or prop in a round, use of de-admin is expected as normal. In situations where direct access to tools like admin chat is required by the player anyways (For things like round flow or reducing Gamemaster workload), the Supervising GM can grant permission to remain an admin while playing in the round. This permission must be explicitly given on a case by case basis.

	~~=== Remaining Admin’d In-Round ===~~

	* Generally speaking, once you have received a role or prop in a round, ~~deadmining~~ is expected as normal. In situations where direct access to tools like admin chat is required by the player anyways (For things like round flow or reducing Gamemaster workload), the Supervising GM can grant permission to remain an admin while playing in the round. This permission must be explicitly given on a case by case basis.

	=== VC Policy ===		=== VC Policy ===
Line 76:		Line 71:
	* After rounds ran by a Jr. GM conclude, the Supervising GM should discuss the round with them. This discussion should include what went well, poorly, things that could be improved upon if the round was to be rerun, and so on. Do not just focus on the negative of the round where possible, discussing what went well is just as beneficial for all involved.		* After rounds ran by a Jr. GM conclude, the Supervising GM should discuss the round with them. This discussion should include what went well, poorly, things that could be improved upon if the round was to be rerun, and so on. Do not just focus on the negative of the round where possible, discussing what went well is just as beneficial for all involved.
	* When a Senior Gamemaster feels as if a Jr. Gamemaster is ready for possible promotion, they may bring the discussion up to the other senior members in a private thread. The starting thread message should include a list of their previously ran rounds (Pulled from the #round-organizing forum).		* When a Senior Gamemaster feels as if a Jr. Gamemaster is ready for possible promotion, they may bring the discussion up to the other senior members in a private thread. The starting thread message should include a list of their previously ran rounds (Pulled from the #round-organizing forum).

	~~== Upcoming Gamemaster/Admin Tools ==~~

	* Selectable Job Presets Without Requiring Uploaded Files
	* Ability to manage job slots for selectable jobs in the lobby, without requiring prototype uploading.
	* Warning/Confirmation on the ‘Spawn Here as Job’ verb for if someone is not whitelisted to the role or has a role ban in that role.

	== Resources ==		== Resources ==

Whisper: /* Miscellaneous */

2026-01-18T04:35:59Z

Miscellaneous

← Older revision		Revision as of 04:35, 18 January 2026
Line 7:		Line 7:
	* '''Supervising GM''' - The GM supervising the round being run, supervises rounds run by Jr. GMs. Works alongside the Lead GM for the round to ensure quality.		* '''Supervising GM''' - The GM supervising the round being run, supervises rounds run by Jr. GMs. Works alongside the Lead GM for the round to ensure quality.
	* '''Lead GM''' - The GM who wrote the script for the round being run.		* '''Lead GM''' - The GM who wrote the script for the round being run.
	* '''Senior GM''' - A senior member of the Gamemaster team. Trusted to supervise Jr. GMs and first time trial rounds submitted through tickets, run rounds without supervision without assistance~~, and mentor members of the GM team~~.		* '''Senior GM''' - A senior member of the Gamemaster team. Trusted with the ability to supervise Jr. GMs and first time trial rounds submitted through tickets, and run rounds without supervision and without assistance.
	* '''Jr. GM''' - Newer members to the Gamemaster team. Someone who has submitted a round through the ticket system, ran it, and been entrusted to stay to run more rounds. Expected to ask questions of Senior GMs to learn and grow as they run rounds while being supervised by a Senior GM.		* '''Jr. GM''' - Newer members to the Gamemaster team. Someone who has submitted a round through the ticket system, ran it, and been entrusted to stay to run more rounds. Expected to ask questions of Senior GMs to learn and grow as they run rounds while being supervised by a Senior GM.
	* '''Trial GM''' - A user who has submitted a script through the ticket system, has had it approved, and is now invited temporarily to the GM team (Granted permissions as a Jr. GM) for the purposes of running that script under supervision of a Senior GM.		* '''Trial GM''' - A user who has submitted a script through the ticket system, has had it approved, and is now invited temporarily to the GM team (Granted permissions as a Jr. GM) for the purposes of running that script under supervision of a Senior GM.
Line 31:		Line 31:
	* Upkeep a positive reputation in the overall community, meaning both in-game and out.		* Upkeep a positive reputation in the overall community, meaning both in-game and out.
	* Maintain kind, respectful, and positive behavior both in-game and out.		* Maintain kind, respectful, and positive behavior both in-game and out.
	* PII and Other Sensitive Information (Ex: Knowledge about admin action in a round, tickets, etc.) must be delicately handled by '''all''' members of the GM team~~. Any such information must be kept within admin chat ingame~~, ~~ahelps, or the pve-gm discord chat~~. Do not discuss ~~any such information without extensive reason to~~ (~~Use your judgement~~).		* PII and Other Sensitive Information (Ex: Knowledge about admin action in a round, tickets, etc.) must be delicately handled by '''all''' members of the GM team, but especially Senior Gamemasters. Do not discuss or share PII (And Other Sensitive Information) outside of the Senior Gamemaster Chat.
	* When a Senior Gamemaster feels as if a Jr. Gamemaster is ready for possible promotion, they may bring the discussion up to the other senior members in a private thread. The starting thread message should include a list of their previously ran rounds (Pulled from the #round-organizing forum).
	* Pings for individual rounds should be kept to only two pings; One for the primer, round information, start time, etc. One for notifying that the server is open to standard connections. Anything else (Ex: Votes for potential scripts or round modifiers, etc) should not be pinged out for but may still be posted in the announcement channel. The message containing the primer must also include the server's IP and a link to the PvE player guide. If the round is being lead by a Jr. GM or Trial GM it must also specify who the Lead GM and Supervising GM are.		* Pings for individual rounds should be kept to only two pings; One for the primer, round information, start time, etc. One for notifying that the server is open to standard connections. Anything else (Ex: Votes for potential scripts or round modifiers, etc) should not be pinged out for but may still be posted in the announcement channel. The message containing the primer must also include the server's IP and a link to the PvE player guide. If the round is being lead by a Jr. GM or Trial GM it must also specify who the Lead GM and Supervising GM are.
	* Gamemasters and Admins alike should refrain from issuing medals on the Normandy server as they will carry over to the Alamo.		* Gamemasters and Admins alike should refrain from issuing medals on the Normandy server as they will carry over to the Alamo.
	* Both the Lead GM and Supervising GM, at minimum, must be present (Even if muted, speaking through text is entirely fine) in the PVE GM voice channel when running a round. This is to allow for easy access and communication if required.		* Both the Lead GM and Supervising GM, at minimum, must be present (Even if muted, speaking through text is entirely fine) in the PVE GM voice channel when running a round. This is to allow for easy access and communication if required.
			* Do not use your admin permissions on the Alamo server in any form.

	=== Handling Problematic Players ===		=== Handling Problematic Players ===
Line 47:		Line 47:
	== SGM Policies ==		== SGM Policies ==

	* PII and Other Sensitive Information (Ex: Knowledge about admin action in a round, tickets, etc.) must be delicately handled by '''all''' members of the GM team, but especially Senior Gamemasters. Do not discuss or share PII (And Other Sensitive Information) outside of the Senior Gamemaster Chat.		*
	* Do not use your admin permissions on the Alamo server in any form.

	=== Remaining Admin’d In-Round ===		=== Remaining Admin’d In-Round ===
Line 70:		Line 69:
	# SGM and Trial GM join the pve-gm voice chat half an hour in advance to the server being open to connections in order to discuss GM/Admin tools and anything else required for the specific round.		# SGM and Trial GM join the pve-gm voice chat half an hour in advance to the server being open to connections in order to discuss GM/Admin tools and anything else required for the specific round.
	# Post round; review thread made internally with the SGMs to discuss if the user should stay. Mandatory 48 hour discussion period on the user/round, to be extended as required.		# Post round; review thread made internally with the SGMs to discuss if the user should stay. Mandatory 48 hour discussion period on the user/round, to be extended as required.
	# ~~Hosts are~~ notified of decision ~~ahead of time~~ to ~~manage permissions.~~		# Trial GM is notified of SGM decision to remain once consensus is made.
	~~# Users are notified of SGM decisions~~ once consensus is made.

	== Jr. GM Rounds ==		== Jr. GM Rounds ==
Line 77:		Line 75:
	* All rounds ran by a Jr. GM will receive a private review thread (Locked to just those with the SGM Discord Role & Whisper) in the Senior GM chat. The purpose of this is to discuss both the good and bad of the round in more detail and track the progress of each Jr. GM. The end goal of these threads should be to gather information to pass on to the Jr. GM of what went well and poorly. Be certain to be able to present this information in a positive manner. The first message in this thread should include some basic information about the round and the message link to the round organizing post for it.		* All rounds ran by a Jr. GM will receive a private review thread (Locked to just those with the SGM Discord Role & Whisper) in the Senior GM chat. The purpose of this is to discuss both the good and bad of the round in more detail and track the progress of each Jr. GM. The end goal of these threads should be to gather information to pass on to the Jr. GM of what went well and poorly. Be certain to be able to present this information in a positive manner. The first message in this thread should include some basic information about the round and the message link to the round organizing post for it.
	* After rounds ran by a Jr. GM conclude, the Supervising GM should discuss the round with them. This discussion should include what went well, poorly, things that could be improved upon if the round was to be rerun, and so on. Do not just focus on the negative of the round where possible, discussing what went well is just as beneficial for all involved.		* After rounds ran by a Jr. GM conclude, the Supervising GM should discuss the round with them. This discussion should include what went well, poorly, things that could be improved upon if the round was to be rerun, and so on. Do not just focus on the negative of the round where possible, discussing what went well is just as beneficial for all involved.
			* When a Senior Gamemaster feels as if a Jr. Gamemaster is ready for possible promotion, they may bring the discussion up to the other senior members in a private thread. The starting thread message should include a list of their previously ran rounds (Pulled from the #round-organizing forum).
	~~= Miscellaneous =~~

	== Upcoming Gamemaster/Admin Tools ==		== Upcoming Gamemaster/Admin Tools ==

PursuitinAshes: Add VC Policy

2025-11-10T02:12:11Z

Add VC Policy

← Older revision		Revision as of 02:12, 10 November 2025
Line 35:		Line 35:
	* Pings for individual rounds should be kept to only two pings; One for the primer, round information, start time, etc. One for notifying that the server is open to standard connections. Anything else (Ex: Votes for potential scripts or round modifiers, etc) should not be pinged out for but may still be posted in the announcement channel. The message containing the primer must also include the server's IP and a link to the PvE player guide. If the round is being lead by a Jr. GM or Trial GM it must also specify who the Lead GM and Supervising GM are.		* Pings for individual rounds should be kept to only two pings; One for the primer, round information, start time, etc. One for notifying that the server is open to standard connections. Anything else (Ex: Votes for potential scripts or round modifiers, etc) should not be pinged out for but may still be posted in the announcement channel. The message containing the primer must also include the server's IP and a link to the PvE player guide. If the round is being lead by a Jr. GM or Trial GM it must also specify who the Lead GM and Supervising GM are.
	* Gamemasters and Admins alike should refrain from issuing medals on the Normandy server as they will carry over to the Alamo.		* Gamemasters and Admins alike should refrain from issuing medals on the Normandy server as they will carry over to the Alamo.
			* Both the Lead GM and Supervising GM, at minimum, must be present (Even if muted, speaking through text is entirely fine) in the PVE GM voice channel when running a round. This is to allow for easy access and communication if required.

	=== Handling Problematic Players ===		=== Handling Problematic Players ===