Government

Updated: 7 January 2026

HSR operates with a structured system of governance. The goal of the government is to improve the server by recieving player input and hosting events.This document outlines responsibilities and clarifications for government roles. These are summaries, not detailed clarifications.

Key Points

Branch Overview

There are two branches of officiality in HSR. The Communal Branch handles community representation and is elected by players. The Development Branch handles server improvement and is appointed.

Communal Branch

Elected

Represents the player base. Has more impact on executive votes.

  • President
  • Ambassador

Development Branch

Appointed

Improves and maintains the server. Reports to the owner.

  • Secretary of Development
  • Admin (see Roles, not part of Government)
  • Developer (see Roles, not part of Government)

Government Roles

The President of HSR is a prestigious and exponential undertaking that only the most dedicated of players should run for. This government position leads Ambassadors and players to improve, expand, and deliver to the playerbase.

Responsibilities

  • Serve the community through events, expansion, and development plans
  • Work closely with the Development Branch
  • Currently retains the responsibilities of the Secretary of Community (see below)
  • Fulfill promises made to the playerbase during their campaign

Election

To win an election, the President must receive the most votes. If a tie occurs, the Executive Council decides the winner.

Voting Power

The President has significant influence in executive votes. They lead the Communal Branch and coordinate with Developers, Admins, Ambassadors, and the owner.

For election details, eligibility, and voting commands, see the Elections page.

The Ambassador is part of the official HSR "government." This role is both a player role and a government role. Ambassadors represent the player base, with representation determined by school population.

Representation Formula

  • Schools must have a minimum of 4 players for representation
  • For every four players a school has, one ambassador may be elected
  • The exact count is determined using a sophisticated algorithm
  • This ratio is subject to change

Three Core Responsibilities

Moderate

Maintain the community and ensure it fosters safe and fun experiences. They have ban, mute, timeout, and pardon permissions across HSR systems, including Discord.

Recruit

Recruit players from their school to join HSR. Recommended methods include bulletin boards, email lists, emails, and personal invitation.

Connect

Serve as a connection between HSR and their school. They may be the Initial Ambassador who first established the school's presence.

Note: Ambassadors can be demoted at any time by the Executive Council.

For player role details, see Ambassador in Roles.

It is the responsibility of the Secretary of Development (SoD) to ensure the gameplay experience of the Minecraft server continues to improve over time for everyone. This means they should interact with the playerbase and plugins consistently.

Leadership

The SoD leads the Developers in progressing the server. This means they have final say on developmental disputes, and ensure that changes to the server are made in good-faith.

  • Developers should seek approval from the SoD for changes
  • Responsible for ensuring gameplay systems are well-documented (internally and externally)
  • May decide where to delegate specific work and assign jobs
  • With approval, may appoint or remove Developers

Content Standards

It is the responsibility of the SoD to ensure that plugins and any other content introduced into the main and dev server are:

  • Safe — Does not damage/alter any HSR system without authorization
  • Fair — Does not give any Developers advantages in any way
  • Enhancing — Improves the general player experience
  • Expandable — Not a "lazy design"

Special Permissions

  • As of now, the SoD is the only standard player with access to CoreProtect (anti-griefing tool)
  • Developmental changes to gameplay should be reviewed by the SoD before entering the development phase
  • SoD's cannot be removed from their position by the Executive Council

Voting Power

The SoD has 1 vote in executive votes. Since the SoD is always a Developer, they also contribute to the combined Developers vote. They may not influence the votes of other Developers.

Changes or additions to the role of the SoD can be made with approval of the owner. Currently, we do not have an SoD.

⚠️ This role is currently not served and has been discontinued. The responsibilities of this role are currently the President's.

Original Responsibilities

The Secretary of Community was designed to lead Ambassadors with the primary goal of expanding and improving the player base.

  • Implement ideas to expand the community (social media, advertisements, etc.)
  • Work with the President to improve the player base
  • May receive endorsement from the owner to establish platforms like YouTube
  • Solve large disputes within the community

Executive Voting

Major decisions in HSR are made through the Executive Council via executive votes. The Executive Council is made up of the Government and the HSR development team. The Communal Branch has more impact on executive votes than the Development Branch.

Vote Distribution

President 3 votes
All Ambassadors 4 votes (combined)
Secretary of Development 1 vote
All Admins 1 vote (combined)
All Developers 1 vote (combined)

Calling an Executive Vote

Last updated 7 January 2026. Subject to change.

Looking for Player Roles?

Learn about New, Player, Alt, Developer, Ambassador, and Admin roles.

View Player Roles →

Ready to get involved?

Learn about elections, eligibility requirements, and how to run for President.

View Elections →