Page 1 of 1

Server Rules for License?

Posted: 2010-03-24 18:12
by deadlie1
Where Can I Find A list Of Rules and Requrements for licensing a server?

Re: Server Rules for License?

Posted: 2010-03-24 18:26
by l|Bubba|l
https://www.realitymod.com/forum/licenseapp.php
PROJECT REALITY LICENSE AGREEMENT
3rd February 2010


IMPORTANT NOTICE READ CAREFULLY:
The terms of this Software License Agreement (the “LICENSE&#8221 ;) shall apply to all versions, editions, and future updates of Project Reality Client and Server software (the “SOFTWARE&#8221 ;) and constitute a legal agreement between you (the “LICENSEE&#8221 ;) and realitymod.com (the “LICENSOR&#8221 ;) .

By downloading, installing, copying, or otherwise using the SOFTWARE, you agree to be bound by the terms of this LICENSE. If you do not agree to the terms of this LICENSE, do not download, install, copy or otherwise use the SOFTWARE.

INTERNATIONAL COPYRIGHT LAWS
The SOFTWARE is protected under international copyright laws. The creations of individual contributors to the SOFTWARE remain the copyright of the original contributing author unless otherwise assigned. By the installation and configuration of an instance of the SOFTWARE on a local or remote computer you are bound by the terms and conditions set forth in the LICENSE and to all applicable International Copyright Laws.

ALL RIGHTS RESERVED
The LICENSOR reserves all rights not specifically granted herein.

SOFTWARE COVERED BY THIS LICENSE AGREEMENT
The SOFTWARE refers to the files included with the Project Reality Server and Project Reality Client software that enable the Project Reality game project to function as either a multiplayer or single player game when used in conjunction with the Battlefield 2 Server and/or Client files. This includes the python code and the server archives that contain original creations, in whole or in part, of the LICENSOR.

Battlefield 2 license terms are not negated by this LICENSE and the terms set forth herein augment the Battlefield 2 license agreement when that software is used in conjunction with the SOFTWARE.

APPLICATION FOR LICENSE
Prior to use of the SOFTWARE the LICENSEE must apply for a LICENSE by means of application to the LICENSOR by the application mechanism.

In the case of client software license application, the application mechanism is included in the SOFTWARE installation process. Acceptance of the LICENSE during installation constitutes automatic application for and granting of a LICENSE by the LICENSOR to use the SOFTWARE as a client installation and use the SOFTWARE in a way that it does not service incoming logon or data requests from computers other than the computer to which the software is installed.

In the case of server software license, the application mechanism is through the Project Reality Website. Application for a LICENSE for the SOFTWARE to function as server software enabled to service incoming logon or data requests from remote computers does not automatically grant a LICENSE for use of the SOFTWARE as a server installation.

The LICENSOR reserves the right to alter the application mechanism at any time and for any reason, or no reason at all, and without notice to LICENSEE.

GRANT OF LICENSE
Upon approval of application for LICENSE the LICENSOR grants LICENSEE a non-exclusive and non-transferable license to use the SOFTWARE only for non-commercial entertainment purposes. Licensee may not disassemble, decompile, reverse engineer, create derivative works of, or modify the SOFTWARE in any way not specified herein. LICENSOR reserves the right to terminate the LICENSE at any time and for any reason, or no reason at all, and without notice to LICENSEE. Additionally, upon breach of any term of this LICENSE, the license granted under this LICENSE shall automatically terminate without any additional notice to LICENSEE.

UNAUTHORIZED USE
Use of the SOFTWARE without a valid LICENSE is an unauthorized use of the software and the unauthorized user will be deemed in violation of the LICENSE. Use of the SOFTWARE when the LICENSE has been revoked will constitute unauthorized use.

REDISTRIBUTION
You may not under any circumstances redistribute any portion of the SOFTWARE provided to you by the LICENSOR.

MODIFICATIONS TO THE SOFTWARE
You may not modify the SOFTWARE without express permission in writing (the “MODIFICATION PERMISSIONS&#8221 ;) from a representative of the LICENSOR. Electronic Messaging via the Project Reality Forums or Private Messaging System will constitute acceptable written form.

Server File Confidentiality
Upon Signing this agreement, you agree with the following:

- I will not distribute the Project Reality v0.9 server files to ANYONE other than the necessary people to install the files to my OWN game server that has been registered. I understand that distributing the server files to anyone else will result in my server license being removed.


Server Side Modding
The following are acceptable mods for publicly accessible internet servers:
- running accompanying scripts to force squad membership
- running accompanying scripts for TK management
- running administrative scripts that do not alter the game play in any way

The following are unacceptable mods for publicly accessible internet servers:
- adjusting spawn times of players or vehicles
- adjusting ticket values or ticket bleed ratios
- adjusting capture times for CPs

If you start a public server on the internet PR uses:
- realityconfig_common.py
- realityconfig_public.pyc

If you start a Passworded server PR uses:
- realityconfig_common.py
- realityconfig_private.py

If you start a Local or Singleplayer server PR uses:
- realityconfig_common.py
- realityconfig_local.py

You can edit the values in realityconfig_common.py.
You can edit the values in realityconfig_private.py.
You can edit the values in realityconfig_local.py.

You CANNOT edit the values in realityconfig_public.pyc.

Upon Signing this agreement, you agree with the following:

- I will not modify or tamper with realityconfig_public.pyc in any form. I understand that tampering with realityconfig_public.pyc will result in server license removal and my PR server being disabled.


MD5 Checks
Upon Signing this agreement, you agree with the following:

- I will run MD5 checks for PR shader files to ensure all players joining my server have equal advantage play. I understand that my PR server is now REQUIRED to run MD5 checks and that failure to do so will result in my server license being removed and my PR server becoming disabled.

**If you need help in getting the MD5 checks setup properly on your server, please ask in the private server admin forums.


Server Name
Upon Signing this agreement, you agree with the following:

- I will include in the name of my PR server the version number. The Current version number is: v0.9. If I need to update my server to a newer version I will also update the version number to reflect what is running on my server. I understand that failing to put a version number in my server name will result in my server license being removed and my server becoming disabled.

***This is mainly so there is no confusion for players joining your server, as well as a good notification for players who are still running older versions of PR that they need to download the latest PR files. Keep in mind the BF2 Server Browser has a limited amount of space so the server name needs to stay under ~20 characters.


If your server fails to meet any of these agreements one of these conditions, you will be notified to comply with the license agreement. If you refuse to obey the agreement, your server license will be revoked and your PR v0.9 server will become "disabled". Players attempting to connect to a disabled server will not be able to connect and CTRL-ALT-DEL will be the only way to quit the BF2 client. We have not needed to use this method yet, and we hope we will not need to use it for v0.9.