Welcome to this book, which covers in detail many aspects of MeridianGroup.

If you are trying to get to our website, you are in the wrong place!

For users of the server, this book might contain some interesting or useful information, however it is generally written for administrators to read, so some of the information might confuse you. If you need help with anything, you can contact us at

Downloading this Book

Although you can download or print this book with the print button in the top right, it will be updated regularly, so it might be worth accessing it online whenever possible.

Other Contacts

If there are any issues with the email system, please contact

If there are any issues with the website, please contact

If there are any issues with copyright or intellectual property, please contact

If there are any issues with abuse from our systems not caused by individuals, please contact

If there are any issues with safeguarding concerns regarding any individual on Meridian, please contact Please note that we cannot provide any information regarding to anything they might have said to a member of staff at Meridian as we operate with a policy of confidentiality.

If there are any other major issues, please contact

For any other issues, please contact

Game Servers

These pages will introduce you to our currently operational game servers and details about the rules, how they run, the concepts behind them, how to connect and who to contact if things go wrong.

FiveM (XM)

The person in charge of XM (FiveM) is: Joe P.


What is XM? XM is a new upcoming FiveM server hosted by Meridian Group itself. XM has been upgraded from it's former server 'Meridian Reborn' Reborn used to be a client side server, Where you had to install your own scripts and used vRP and that was very unorganised and crossed over with a lot of other plugins.

Since that we shutdown Reborn and are now developing 'XM' to make a more user friendly experience and make an easy to use RP experience. This means Self-progression, with server side menus, Jobs, Car Shops, Weapon shops, Banks and your own money system!


  • Use the F1 phone as a primary source to contact any services.
  • Once pulled over by a cop you can not run or else it will be counted as FailRP
  • You can only raid a shop 1 time a day.
  • Admins words are final
  • FailRP will not be tolerated at any times.
  • Spamming chat will result in a punishment.
  • The NLR applies at all times. If you die you cannot return to the previous role-play/scenario.
  • Do not impersonate any government agency.
  • Play realistically as you would in real life. Don't be silly...
  • No trolling, cop baiting.
  • No out of character talk. Unless using /ooc
  • No terrorist or rape/sexual role-play is allowed. (This includes spawning military vehicles).
  • No racial/religious / gender discrimination, in or out of role-play.
  • Do not leak any personal information including direct messages.
  • Role-play all vehicle crashes at all times disregarding the severity.
  • No meta-gaming / power-gaming.
  • Respect all members, not accounting the current situation, treat everyone equally with respect.
  • Do not drive on airfields.
  • Do not run while you are cuffed.
  • If you get tased twice, don't run or else it will be counted as failrp
  • No stealing ANY emergency vehicles.
  • Do not advertise social media, other servers, or websites. (Including /pm or /text).
  • No colours/callsigns/Emojis in your name. (Only if allowed by Owners)
  • Make sure to always obtain weapons realistically by going to a gunshop.
  • No suicide role-play.
  • Do not exploit commands.
  • No nude characters.
  • Make sure to always contact a mechanic for vehicle repairs, (If no mechanics are not online then entering garage and back again will be tolerated)
  • No VDM
  • The spawning of objects/props are prohibited.
  • You MUST obey the admins words at all times
  • Make sure to always role-play taking out a weapon.
  • Executive decisions and final outcomes are final.


The people in charge of Minecraft are:


The Minecraft server 'Atlarax' is a friend based Minecraft server that is only here the 'close' people of Meridian Group to have fun on and collaborate together.

This server will not be open to the public.


The Minecraft server has not a lot of restrictions on there so there has to be rules set to make sure that everything on the server is fair and well managed.

The Rules are the following:

  • Greifing is not tolerated at ALL, This will result in a semi-permanent ban! (This includes, Stealing from others, Killing of their animals aswell)
  • Any form of Cheats or Hacked clients are not permitted on the server. Soft hacked clients are permitted. Cheats to give you an unfair advantage are not!
  • Redstone clocks that are purposely made to 'lag' out the server are not allowed on the server and will result in the 'clocks' being deleted and a warn.
  • If you are entering someone's property please abide by their property rules.

KSP (Universe)

The person in charge of Universe (KSP) is: Lily H.


The KSP server uses DarkMP and a selection of mods. The mods are currently hosted as a git repository in the MeridianGroup Keybase group. If you wish to join, please contact the person in charge.

To join, from the DarkMP menu, connect to


The KSP server is a sandbox world which is intended for building any and every craft. It is intended to be a welcoming place for everyone, so please do not build craft which cause damage to other people's craft.

You are welcome to create a fictional company in game to collate your craft. Please do not infringe on intellectual property whilst naming your company.


  • Craft must not be designed to cause excessive lag.
  • Craft must not be designed to damage other people's craft or bases.
  • You must not use another fictional companies name.


If you have any issues connecting, please contact the person in charge.

If you have issues with the mods, please contact the author of that modification.

New Game Servers

Every so often a user may wish to open up a new server on Meridian. There are a few options available. The only thing we ask is that you abide by a few rules which mainly are common sense. We don't want to take the fun out of it, but it is important that we are all vigilant and keep Meridian a safe group of people!

Host on Your Own Machine

Hosting a server on your machine may not seem like a very useful thing, but by using the MeridianGroup VPN players across MeridianGroup can connect to you without port forwarding and without using a public service which may not handle your data safely.

Host on MeridianGroup's Infrastructure

This option costs money, but generally a lot less than hosting a server by yourself! We can help you set up and help you maintain your server, whilst providing you with powerful and reliable infrastructure.

Still take full control over your server, as we provide you with the tools that the professionals use. It's a steep learning curve, but it is worth it and gives you valuable skills in technology and server management. You could even put it on a CV!


This section of the book covers how administration is performed on MeridianGroup's server, and what people should do if there are issues. It is generally not going to be useful for users of the server, and is written for the administrators.


The people in charge of Discord are:


Moderating Discord is very important, as it is the bit of MeridianGroup which most people see on a regular basis.

Immediate Action by Administrators

Administrators should screenshot the message and who it was sent by, then remove it as soon as possible and report it to one of the people in charge.

Content Containing Flashing Imagery

Any video which contains flashing imagery must be clearly marked before it is posted warning of flashing imagery. .gif moving images and videos which autoplay with flashing imagery are not permitted at all.

A user who posts flashing imagery will be subject to the following disciplinary action:

  1. Warning
  2. Kick
  3. Ban for one week.

MLMs, Sponsorships and Discounts

Any MLMs, Sponsorships or Discount Codes which benefit a user of the server in any way (monetary or otherwise) are not permitted. Any user found to have posted an MLM, Sponsorship or Discount Code will be subject to the following action:

  1. Warning
  2. Kick
  3. Ban permanentely.

If you still wish to post a discount code, explicit permission may be obtained from a member of staff.

Offensive Content

Any content that is offensive either by directly causing offense or by causing offense through indirect reference to current and/or previous events is not permitted.

A user who posts offensive content will be subject to the following disciplinary action:

  1. Warning
  2. Kick

NSFW Content

NSFW is Not Safe For Work. Content of this nature includes:

  • Sexual imagery
  • Sexually suggestive imagery
  • Imagery involving any nudity beyond undergarments

NSFW content is permitted only in channels marked clearly as NSFW using both Discord's system for marking them as NSFW and by clearly stating 'NSFW' in the name of the channel.

Any material that is deemed NSFW that is not posted in a channel marked as NSFW is not permitted and the author will be subject to the following disciplinary action:

  1. Kick
  2. Ban for one week.
  3. Permanent ban.

NSFL Content

NSFL is Not Safe For Life. Content of this nature includes:

  • Extreme gore
  • Dismembered limbs
  • Visible death of any kind

Content of this kind is forbidden entirely on the whole of the Discord. Any user found posting this sort of material will be subject to the following disciplinary action:

  1. Warning
  2. Immediate kick from the server
  3. Immediate six month ban from the server

Note that a user banned for this reason cannot have their ban shortened unless the content is proven to be posted by another user.

Provocative Content

Any content that provokes another user beyond a reasonable amount and causes excessive anger or distress is not permitted anywhere on Meridian. Any content of this such will be dealt with severeley. Users who continue to provoke another after clear warning will be immediatley banned for one week, or at the committee's sole discretion.


The people in charge of Minecraft are:

Useful Commands

  • /help - This will tell you the list of commands in game that will help you.
  • /pm <username> - This is the command to Private Message someone in game.
  • /invsee <username? - This command will let you see into a players inventory.

General Information

Universe (KSP)

The person in charge of Universe (KSP) is: Lily H.


Administrating KSP is a challenge because there are not many controls available to administrators. The main issue will come down to rude, inappropriate or offensive names or chat messages. If people are found to be doing this, they can be blacklisted by contacting the person in charge. Please screenshot their chat message and username.

Textual Content

Any textual content must not be too rude, for example by using strong language, inappropriate, for example by using material of a sexual or sexually suggestive nature, or offensive, for example by discriminating against a group of people.

A small joke might be acceptable, but this will be at the discretion of the administrators online and the person in charge.

XM (FiveM)

The person in charge of XM (FiveM) is: Joe P.



The person in charge of Branding is: Lily H.

MeridianGroup uses consistent design features to maintain a clear brand image. This page sets out some of the guidelines we follow.

If you require any branding materials, please see the GitLab Repository (please note that you must have permission from the person in charge to access this repository).


The MeridianGroup font is a clear way of showing affiliation. The font must only be used in projects approved by the committee. It should be used sparingly and only for product titles. For headings, the font 'Raleway' should be used. For paragraph text, the font 'Source Sans Pro' should be used.


Services closely affiliated with MeridianGroup should include a reference to either 'Meridian' or 'MeridianGroup' in their title, however this should not form an integral part of the name of the service. For example, XM is permitted, whilst MeridianXM is not.

The MeridianGroup logo can be used for any purpose associated with MeridianGroup. However, the following guidelines should be followed:

  • The logo should not be blurry or pixelated.
  • The logo should have sufficient spacing around it.
  • The logo should never be stretched.
  • The logo must never be used in a manner which suggests affiliation with MeridianGroup, unless you are affiliated with MeridianGroup.


The current colour pallette follows the original specification, which is available on request from the person in charge.


At MeridianGroup, we have a policy of being transparent about what we do and how we do it. This means that we try to publish information about what we are getting up to and the approaches we are taking.


  • Any situation which requires confidentiality
  • Personal data
  • Trade secrets
  • Security flaws which have not been patched

Supporting our Members

As a community, we try to support our members where appropriate and to the best of our abilities. In any situation where professional help is the best way forward, we try to encourage people to seek help.

Some charities we will recommend are:

  • Relate provide help and information to do with relationships (in family and romantic contexts), sex, family life and divorce.
  • Childline provide help for under 18s about any aspect that might be important.

Connecting with Us

This section of the book details how to connect to MeridianGroup services.

Most of these services require having an account with us. If you do not have an account but still wish to use our services, please contact and we might be able to set you up with an account (and an email address).


The person in charge of the Email System is: Lily H.

When you are working with MeridianGroup, it is likely that we will provide you with an email account. This can be accessed using our webmail system, or by using the details below:

IMAPS (incoming):

  • Hostname:
  • Port: 993
  • Username: your full email
  • Password: your password
  • Security: SSL/TLS

SMTP (outgoing):

  • Hostname:
  • Port: 587
  • Username: your full email
  • Password: your password
  • Security: STARTTLS (accept all certificates)

Alternative services might be available. If needed, please contact the person in charge.

Your password can be changed (as well as further account management) at the Account Management system.

Meridian VPN

The Meridian VPN runs on OpenVPN.

Note that if you install OpenVPN on Windows, it must be run as an administrator to work correctly.

If you have an account with Meridian, you can have an OpenVPN profile emailed to you by going to the VPN request page and logging in. If you don't have an account then you won't be able to connect.

Using the VPN allows you to host 'LAN' games which are available to everyone else on the VPN. This makes it particularly easy to host servers. The VPN also allows special access to some internal services available from Meridian.

Note that the VPN Meridian uses is not the kind that hides your internet traffic.

Server Management

The person in charge of Server Management is: Lily H.

This applies only to servers hosted on MeridianGroup equipment.

Getting Connected

Generating your Key

In order to manage a server, you will need to get connected and sign in to your account. As a security measure, we use SSH keys rather than passwords for public-facing authentication.

In order to generate your SSH key on Mac/Linux or Windows with CygWin or MinGW:

$ ssh-keygen

The public part of your key will then (by default) be available in ~/.ssh/

In order to generate an SSH key on Windows without CygWin or MinGW, you will need to use PuTTYgen, available online. Start the program and click the 'Generate' button. Move your mouse around within the window to generate randomness. The public part of your key will be displayed in the text box at the top of the window. Make sure to save the private part of your key!

Please generate at least 2048-bit keys using RSA.

Once you have generated your key, please send the public part of your key to the person in charge, who will add it to your account. Note that multiple keys can be used for one account, so it is a good idea to use a different key for each machine you connect from to increase security.

Connecting to SSH

One of the most useful tools you will have access to is secure shell. This allows you to issue commands directly to the server.

In order to connect on Mac/Linux or Windows with CygWin or MinGW:

$ ssh <hostname>

In order to connect on Windows with PuTTY, enter the hostname into the hostname box, then from the left select: SSH > Auth. At the bottom of the right portion of the window there will be a space to select your private key file.

You will be prompted to provide your username, after which you should automatically log on with your private key.

Connecting to SFTP

As well as using SSH, you can also use SFTP (not to be confused with FTPS). This allows you an easier way to transfer files. Setup is the same as above.

Some recommended SFTP clients are:

A Quick Guide to SSH


To navigate around, you can use the command cd, short for 'change directory'. Specify cd followed by the folder you wish to descend into. To go up a folder, use cd ...

To list the contents of the folder you are currently in (also known as your working directory), type ls, short for list.

Editing a File

To open a text file for editing, type nano and then the name of the file, for example:

$ nano config.cfg

For more experienced users, vim is also available.

Controlling your Server

Unless you have been told otherwise, your server will be controlled through systemd. This means a few things:

  • Your game server will automatically start if the whole server restarts
  • Your server will save all it's logs to a central location

In order to see the status of your server, and the last few lines of it's log:

$ systemctl status <server name>

where <server name> is the name of your server as provided to you by the person in charge. For example, for XM, the FiveM server, you would run:

$ systemctl status fivem

If you wish to control your server, you can run the following commands:

$ sudo systemctl start <server name>
$ sudo systemctl restart <server name>
$ sudo systemctl stop <server name>

Note that you need to use the word sudo here. This allows you to execute some commands as the 'superuser', a user which has permission to do anything on the system.

Viewing logs

To view logs, you need to view part of the journal using the command:

$ journalctl -u <server name>

Where you view the journal unit for your server. To find out more about the clever things journalctl can do, see the manual by running the command man journalctl.

Using git

git is a version control system. It is important to remember throughout this document that it is intended to keep a history of changes and a full history of versions of your code, or other files. The fact that using git provides backups at each stage should always be considered a convenient side effect, not a deliberate feature.

Downloading a git repository

If you have a repository online which you wish to download with git and use, you can execute the clone command:

$ git clone brand

It is worth spending a moment to break this command down:

  • The git clone part runs the git program and tells it that you wish to clone a repository.
  • The part is a URI which specifies where the repository is located. It can either be an SSH type location, which will usually start, or an HTTPS type, which starts with https://. SSH type is preferred, but requires an SSH key to be set up with both the machine accessing the repository and the git server.
  • The brand part specifies where to clone the repository to. It must be either an empty or non-existant folder. . can be used to clone to the current directory.

This will download the repository ready for use.

Making a new repository

To make a new repository go into a folder with which you wish to start using git and run the command:

$ git init

Then add the remote (the git server) with the command:

$ git remote add origin

The URI to use should be given to you by your git host.

Syncronising changes with the remote

You might not always be the only person making changes to your repository. To see if any changes have been made, run:

$ git fetch

If running this shows nothing, no changes have been made. Otherwise, it should suggest how many changes. If you wish to actually then download the changes to your copy of the repository, run:

$ git pull

If you have made changes to the repository that need to be uploaded to the remote, run:

$ git push

Note that if this is your first push, you may need to explicitly set the master branch on the 'origin' remote:

$ git push -u origin master

Making changes

When making changes to files in a git repository, they start off unstaged. These will not be uploaded. When you have completed adding a feature to your repository, ie. something with making a version for, you can add the files you have changed, or remove them if you have deleted them:

$ git add file/path
$ git rm file/path

Once you have staged all the changes with the above commands, you can commit your changes to the repository. Note that at this stage they are still saved locally on your computer:

$ git commit

You will be prompted to add a message explaining what your commit contains. You can then push.

How often should I make commits?

Do make commits for:

  • A new feature that is complete and working
  • A new asset or collection of assets
  • A change or improvment to code

Do not make commits for:

  • An incomplete feature
  • An untested portion of code
  • A collection of files which are completley unrelated

Moving on to more complex situations

Git is a powerful tool, and this only covers the very basics. It is worth spending some time to learn what git can do. It might be worth finding out about:

  • Branching and Merging
  • Amending commits
  • Resolving merge conflicts
  • Rolling back changes that have broken something
  • Tags
  • man git

GDPR Requests

On occasion, people may make requests under the Data Protection Act for a copy of their information to be sent to them. In this case, administrators, if able, should take the following actions. If unable, they should raise the case with a more priviledged administrator.

Stores of Information

  • Mailing Lists
  • Databases
  • Unix User Accounts (if applicable)
  • Mail (if applicable)
  • Invoicing System

Collecting the Information

Mailing Lists

From the mailing lists, the user's personal details and message status and clickthrough details should be collated, probably as a .json file as part of an export from the API.


A .csv export of any records from tables relating to the subject. Ensure that no user data of other users is compromised.

Unix User Accounts

If the user has a Unix account on any MeridianGroup controlled server, the details of this account should be collated. This should include entries in /etc/passwd, /etc/shadow and /etc/groups.


If the user has an email account, the details of the account, any aliases and a .zip file of the user's email inbox should be collated.

Invoicing System

If the user has been invoiced previously for any reason, a copy of all previous and future invoices should be provided, and any additional personal details stored on the invoicing system.

Sending the data

Once collected, the data should be sent as a .zip file containing all relevant data in separate folders. Before any file of this kind is transmitted, it must be checked by a member of the committee, who can be contacted at