Skip to content

Instantly share code, notes, and snippets.

@emilekm
Last active September 10, 2019 11:44
Show Gist options
  • Save emilekm/c7c7d639eca2b9fb93146a78fe8727a5 to your computer and use it in GitHub Desktop.
Save emilekm/c7c7d639eca2b9fb93146a78fe8727a5 to your computer and use it in GitHub Desktop.
[WIP] New PR community/server sketch

This document describes my vision on what is expected of this new PR community/server.

The whole idea comes out of PRTA not handling some of the issues (mainly lack of transparency on handling issues and hitreg). Second issue (hitreg) should be fixed by either using Windows machine or Linux without containerization (requires testing).

The transparency is a backbone of this community. Everything that is being written down should be considered public knowledge and participants should feel responsible for their words.

I decided to use a ticketing system for player<->administration interaction (appeals, reports). I implemented the ideas using Github organization here. The use of a ticketing system discourages any rubish/offtopic discussion, since there is no space for that. This also implies that forum software could be used for this type of interactions between associated players (members) in future, for now I'd like to stick with Discord and Teamspeak.

Server configs, rules and other documents should be stored as git repositories on selected git platform (currently Github). Git is a versioning system, allowing you to track changes in files. Github has an intuitive editor so you don't need git knowledge to be able to contribute changes.

The infrastructure doesn't matter as much as long as the server is interesting and people want to join it. As we experienced it firsthand most of the time people will join more populated server - unless it's an event.

At the begining I'd like to only run events. The server shouldn't run daily, I don't want to seed it like other servers do - I will start it when I'll know that it can be populated. I already spoken with some of the clan leaders and they are interested in organized PR matches. This could work in many different ways:

  • events with some custom mechanic (my part would be to create those)
  • clan matches (like PRTA's Inter-Unit battles)
  • public matches with designated SL's (from clans), pubs could join existing squads (but not create), SL's could refuse to play with them, these would get autokicked for not being in squad. This could discourage people from joining but could also create a need to behave properly to not be kicked. An option would be to have training/pub squads with SL's wanting to lead these people.

Some derivations of these could be created in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment