Below are other rules applying to the TJO affiliated games, both Ilum v1/v2/Legacy & Dantooine.
Talking in all caps in-game can be considered spam. If someone attempts to mass spam a server to result in lag, they will instantly be demoted to Force Sensitive. If they are already at the rank of Force Sensitive, any Jedi Instructor+ can enforce the warning system upon them & any Jedi Master+ can enforce the banning protocol system upon them with enough evidence.
A TJO banned person should be banned from any TJO game upon joining.
You are allowed to kill unarmed Hostiles; however, spawn-camping &/or spawn-killing is still not tolerated.
Members of the Jedi Order are required to wear Jedi robe attire in-game in public servers and TJO-events.
Only shirt and pants will be enforced; Jedi attire is what a reasonable person would assume to be a Jedi.
Only applies for Jedi teams and their divisions. (TG and Taskforce use their respective uniform options in their dojo, Lorekeepers don't have a mandated division attire)
Staff will be asking you to equip a Jedi attire through avatar or in-game uniform menu.
All other accessories are allowed.
You are allowed to wear your own robes; it just has to resemble Jedi attire of some sorts.
The usage of ANY saber when combined with ANY trooper classes that include a blaster is strictly prohibited. Those who choose to do so will receive a punishment and it will fall under the same category as "glitching."
(If you have a custom saber, you can't use a gun with it or if you have a custom gun, you can't have a saber)
Other teams should not go into the Sith spawn area (defined by anything inside the ice circle surrounding their base).
Do not spawn camp.
Hostiles are permitted to raid the Council Chamber so long as the Council is not using that room; the Jedi may also walk into that room for the sole purpose of killing hostiles that enter if no Temple Guards are present.
Shadow blocking and any form of it is against the rules and is considered glitching if done deliberately.
If a hostile has their saber ignited or is inside the temple, you may engage at will.
If you are attacked from out-of-range with either a gun or a Force power such as Telekinesis or Lightning, you may engage at will.
Spawn abuse of any form including misuse of the spawn barriers (eg to teleport away from danger) is prohibited.
The Spawn Kill & Spawn-Camp rules only apply to the Jedi Temple and the Sith Cave bases. Points "A, B, C, D, E" are exempted from this rule.
Using the speeder to avoid the ragdoll of force movements is considered a glitch and will be punished harshly. The same applies to the speed-glitches that can be done with your saber.
You're not allowed to disrupt people officially assigned as Guards by the Host while they're hosting a training (as Jedi). This will be considered disrupting the training and will have the same punishment.
What is spawn kill?
Spawn kill is the act of killing (KO'ing) individuals in their own spawn. Any form of spawn kill is against the rules.
What counts as spawn kill?
Entering the enemy spawn zone, for example, entering the Jedi Spawn as a Sith.
On Ilum, spawn kill can occur in the Sith spawn, Temple Guard spawn (right in front of the jails in the back of the Temple), & the Jedi spawn (which has a barrier at the end of the hallway; first right from Temple entrance).
Firing blasters & using Force from far away to attack individuals in their spawn.
Camping (staying) right outside an enemy spawn, with purposeful intent to attack the enemy once they exit.
Dragging an enemy player out of their spawn zone via using any force ability. (Ex: Using Force Grab to grab a Jedi out of Jedi spawn room when they are standing behind the barrier.
This goes especially towards Jedi and its formal division members (Taskforce and Temple Guards) who wait right outside of the Sith spawn & Sith who wait right outside of the Jedi spawn.
What does not count as spawn kill?
Being in a justified position that is out of range from an enemy spawn.
Not being in an enemy's spawn in general.
On Ilum, you can be near the fallen pillars outside from the Sith spawn as a Jedi/Ally.
This is a list of all of the Admin commands that you can and cannot use whilst you are within the server. Please take the time to read these, otherwise you could be punished for using a banned command.
Commands are to be used for actual situations consisting of a problem or issues in TJO such as dealing with rule breakers, hosting trainings, etc.
Do not try to solve “problems” like someone not being able to find a crystal so you just bring them there. Commands are only to be used for situations where they are a necessity and the outcome will benefit the group/game/server/etc.
Don’t use commands on a public server for unofficial events ( like using :n to announce you’re hosting your own dueling tournament ); that falls under the category of admin abuse. This is assuming you are under the rank of Jedi Council and/or were not given permission by a Jedi Councilor.
When you jail someone, do :team ( jailed person’s name ) visitor and :reset ( name ) so they don’t die and so they don’t have their tools.
When using a command that involves another person, like jailing someone, make sure to type out as much of their name as possible. You don’t want to end up jailing multiple people.
Never use commands that affect a large amount of people. For example, don’t respawn the entire Sith team or refresh everyone in a server. If you MUST use commands that affect so many people, it is better to check in with a Council member to make sure you are all cleared for it.
All commands are to be logged through the use of :logs ( reason you used said command. ) The only commands you do not have to log are :name, :pm, :n (only when used for a training), :afk, and :warn.
Using a single log to account for many commands such as :logs all commands are for ( blank ) is somewhat allowed. It is suggested to be used only during trainings or trials but for other things it is usually not recommended. As long as we knew why each command was used, it should be fine though.
If someone accumulates at least 15 warnings in game, they are to be auto banned from the game. If they wish to be unbanned, they must DM a JC to appeal their warnings.
Divisional Staff members that have admin powers CANNOT use their administrative powers for any reason, UNLESS there is an exploiter in the server and no high ranking member is present, in which case you may kick them.
:logs (Use this to log every command you do apart from the ones mentioned above)
:chatlogs (Use this for an actual reason, like finding out if someone disrespected another)
:exploitlogs (Shows who exploited; might not always be accurate)
:showlogs
:warnings (username)
:warn (username) (When someone breaks a rule, you warn them)
:jail (username) (Use this after a person was warned and keeps acting up, warn them again once jailed)
:kick (username) (Use this after the person jails keeps acting up, and again if they persist after the first kick. Division staff may use this command to kick exploiters.)
:kickwarn (username) (Same as kick except it additionally issues a warning; both commands can be used automatically on spammers)
:ban (Use this after the second kick, auto ban exploiters, or use if absolutely needed)
:view/:watch (Only use for (suspecting) rule breakers)
:mute (Allowed if two+ warnings are given or for a mass spammer. 5 minutes maximum usage).
:age
:shutdown (Council member+ permissions needed. Server must be in really bad shape, for example extreme lag)
:removetools (Council member + perms needed.)
:showtools
:health (Allowed during duels/trainings)
:sit (Do not overuse this command)
:cmds/:commands
:pm (Don’t spam this, try whispering first unless really needed)
:name (Normally used during events)
:countdown [DO NOT USE IN PUBLIC SERVERS]
:cdpm user,1user2 time (The same that countdown, but only for the users specified)
:bring, :tp, :to (Do not use just to get places or to people)
:ff (Only in Ilum 2 or vips, for gathering purposes to protect from hostiles)
:h (You can occasionally use this during a training for directions)
:n (Use this a maximum of two times for event announcements in a server)
:setmessage (Use it when you are starting a training or tryout)
:team
:unteam (Only for Ilum 2, for guarding purposes since there are no barriers nor Temple Guards.)
:heal
:guard CT/auditorium (Sets a training barrier when you close a training) - Dantooine ONLY
:barrier mats/library/spawn (Sets a training barrier when you close a training) - Legacy Ilum ONLY
Any command that hurts others, forcefully changes someone’s character, takes away free will, that alters the game ( with the exception of :btools which is Council+ ), etc. is banned.
Any command used as a rank below Jedi Instructor for non-training/tryout/trial purposes (apart from kicking exploiters).
Any command that has no use in any dire/unique situation and is most probably disruptive that is not in the allowed commands section is banned. This includes :fling, :disco, etc.
:mod or :admin is banned in all instances, and may not be used in private servers.
Banned commands are allowed to be used on private servers, as long as their effect is not permanent and an event is not on going.
Banned commands or admin abuse in general is not allowed on someone else's private server if the owner tells you to stop.
:fly ( Council+ )
:god ( Council+ )
:clip/:noclip ( Council+ )
:btools ( Council+ )
:resetstats ( Council+ )
:change ( Council+ for raids/trainings )
:place ( Council+ )
:shutdown (Needs authorization by Council+)
:removetools (Needs authorization by Council+)
:databan ( Grandmaster ONLY )
:clearwarnings ( Council+ permission required; banned on private servers too if Master" or below )
:tempmod/:tempadmin ( May be used on private servers ONLY. )