Merge branch 'master' of ssh://play.qtechofficial.com:9940/QTechIndustries/fermi
This commit is contained in:
commit
539841fb60
2 changed files with 32 additions and 1 deletions
31
README.md
31
README.md
|
@ -0,0 +1,31 @@
|
|||
# Fermi modpack rules
|
||||
|
||||
### Winning/Losing Conditions:
|
||||
Win - Eliminate all other players
|
||||
|
||||
Loss - All of your bases have been destroyed, and you cannot rebuild with the already available resources, or your in game name is QTechQuantum
|
||||
|
||||
### Definitions:
|
||||
Base - A structure where any type of processing or storage occurs that is not directly related to extracting raw resources.
|
||||
|
||||
Raid - An entrance into another's territory for the purpose of seizing goods, valuables or causing destruction.
|
||||
|
||||
### Misc:
|
||||
Power generation is considered an extension of anything it is powering, not a separate entity.
|
||||
|
||||
### Rules:
|
||||
1. Do not search for bases/raid bases until the grace period has ended
|
||||
1. Grace period ends on November 13th at 11:59PM Eastern Time*
|
||||
1. If you find a base on accident during these periods, that's fine.
|
||||
1. Doing PVP in the grace period is very frowned upon and rude
|
||||
1. Bases must be within 2500 blocks of spawn (0,75,0) and in the Overworld (non base stuff can be anywhere)
|
||||
1. Bases cannot be blast-proof (however, blast resistance is highly recommended)
|
||||
1. No raiding people when they are offline
|
||||
1. No unraidable storage (personal safes, alt accounts, etc)
|
||||
1. No hacked/utility/minecraft enhancement clients
|
||||
1. No ESP (except for things already included in or made in the modpack)
|
||||
1. To raid bases, you must blast in using missiles
|
||||
1. To raid nonbases, you may use any explosive
|
||||
1. You cannot teleport within 250 blocks of an enemy base
|
||||
1. Exceptions are: `/spawn` and any vanilla means
|
||||
*May change by popular vote
|
|
@ -198,7 +198,7 @@ opencomputers {
|
|||
# code can easily be used for exploits, running arbitrary code on the
|
||||
# real server! I cannot stress this enough: only enable this is you
|
||||
# know what you're doing.
|
||||
allowBytecode=false
|
||||
allowBytecode=true
|
||||
|
||||
# Whether to allow user defined __gc callbacks, i.e. __gc callbacks
|
||||
# defined *inside* the sandbox. Since garbage collection callbacks
|
||||
|
|
Loading…
Reference in a new issue