|
| |
|
|
| |
| DSB Public Rules |
NB: Player's are responsible for reading the rules
and knowing their contents. It is no excuse to plead
ignorance when the rules are easily accessible.
1. Zone Staff
1.1 DeathStarBattle (DSB) is comprised of moderators
utilising the Op> tag, more commonly known as Op's, e.g.
Op>Helper.
1.2 There are other moderators in the zone that do not use
the Op> tag, but rather are Senior Staff (e.g. Smod or
SySop) identifiable by the DSB banner and, like Op's,
belonging to the DSB STAFF squad.
1.3 Only those individuals with an Op> tag or in DSB STAFF
are authorised to enforce the rules of the zone.
1.4 Players using these tags without prior authorisation
commit an offence. In such cases, the player will be asked
to remove said tag and in the event that they do not they
will banned from the zone for a period of no less than one
day.
1.5 If
a player needs help or to report a problem, they should
use the '?help' or '?cheater'; commands.
1.6 In specifically designated areas within DSB, called
'Events', members of Staff called 'Event Referee's', more
commonly ER's, can be distinguished by the ER> tag and
belonging to DSBe STAFF.
1.7 As with Senior DSB STAFF, DSBe has Senior Staff which
do not use the ER> tag, but are identifiable by belonging
to the DSBe STAFF squad.
1.8 All Event complaints are to be directed towards an ER
and not to an Op.
1.9 Op's do not have any official power in Events ('elim'
and the 'practice arenas' being the only exceptions when
an ER is not online), just as ER's do not in public arenas
(the 'duel' arena included).
1.10 If a player wishes to play in an event, they should
use the '?host' command and request an Event from the
range offered by the DSBe STAFF. A full list can be found
in the zone's news.txt.
1.11 If player's wish to have an 'exclusive' practice,
that is, one where only squads playing against one another
play, then they should use the '?closed' command which
will indicate to Staff that only those invited should be
playing.
2. Legal Ships
2.1 Freq 0 (Imperials) uses ships 1-4.
2.2 Freq 1 (Rebels) uses ships 5-8.
2.3 DSB utilises bot's; which automatically (unless
otherwise stated in the news.txt that this has been
temporarily suspended) sets players to the appropriate
frequency.
2.4 In the event that the bots are not functioning the
Operators' in the zone, or Op's will inspect to ensure
that players ships correspond to the frequency they are
on.
2.5
Op's will post an arena message stating that the bots are
offline, and as such players will be given a reasonable
period of time to adjust.
2.6 The terminology for such a situation will either be
that the bots are offline, or to get legal.
2.7 It is, however, the players responsibility to ensure
that they are on the appropriate frequency.
2.8 In the event that players have not corresponded their
ship to the frequency they are on, Op's are authorised to
shipreset players to the appropriate frequency.
2.9 In the event that a player continuously disobeys the
Op's command, a player will be warned three (3) times,
after being shipreset, to get legal.
2.10 If after the third (3rd) warning, the player still
does not comply with the rules, the player will be placed
into spectator mode, the Op will proceed to explain the
violation, and then the player will be freed once this is
understood.
2.11 If after being freed from spectator mode, the
violator still does not comply with the rule the violator
will be given one (1) warning; after which time the Op is
authorised to ban the violator for ten (10) minutes.
2.12 If upon returning to the zone the violator still does
not get legal the Op shall repeat the same process laid
out in rule 2.11, but supplemented with twenty (20)
minutes.
2.13 Rule 2.12 applied but supplemented with thirty (30)
minutes.
2.14 Once the violator has been banned from the zone for
thirty (30) minutes the Op on duty will report the
incident to Senior Staff who will then evaluate the
situation and has the discretion to ban the violator from
the zone for a longer period of time, depending on the
relevant circumstances.
3. The No Kill Zone
3.1 When a player enters DSB, they are placed inside
what is called the 'No Kill Zone';.
3.2 The No Kill Zone, or more commonly known as, the NKZ,
is a safe area in public arena where players begin their
game play.
3.3 As the name suggests, in this area killing of other
players is strictly prohibited.
3.4 Players are said to be in violation of the NKZ rules
when they:
i. Fire at other players inside the NKZ;
ii. Bomb at other players inside the NKZ;
iii. Mine the NKZ;
a. This includes the entire area within the 'chain-link'
fenced which surrounds the NKZ; and
b. The mining below the two (2) rotating rocks directly
above-left of the NKZ.
iv. Baiting another player into the NKZ, which includes,
but does not exclude, attacking another player and then
running inside the NKZ, thus causing the other party to be
in violation of the NKZ rules; and
v. Any other behaviour which results in direct conflict
within the NKZ.
3.5 Players who have violated the NKZ rules will be given
three (3) warnings.
3.6 If after the third warning the player still violates
the NKZ rules, they will be placed in spectator-mode,
where the Op on duty will proceed to explain the rules to
the player, and then release the player once the Op on
duty is satisfied that the player understands the rules.
3.7 The procedure in rule 3.6 will continue for another
two (2) times, except instead of three (3) warnings, only
one (1) warning will be given, followed by being placed
into spectator-mode after each warning.
3.8 If after release from spectator-mode the violator
continues to break rule 3.4, the Op on duty is authorised
to ban the violator for ten (10) minutes from the zone.
3.9 Once ten (10) minutes has expired, the violator will
be allowed back into the zone to resume game play.
3.10 If upon returning the violator breaks rule 3.4, the
violator will be warned one (1) time, after which point
the violator will be placed into spectator mode.
3.11 If after release from spectator-mode the violator
continues to break rule 3.4, the Op on duty is authorised
to ban the violator for twenty (20) minutes.
3.12 Rule 3.9 applied but supplemented with twenty (20)
minutes.
3.13 Rule 3.10 applied.
3.14 Rule 3.11 applied but supplemented with thirty (30)
minutes.
3.15 Once the violator has been banned from the zone for
thirty (30) minutes the Op on duty will report the
incident to Senior Staff who will then evaluate the
situation and has the discretion to ban the violator from
the zone for a longer period of time, depending on the
relevant circumstances.
3.16 The rules on the NKZ still apply irrespective of the
description provided of that NKZ above.
4. Team Killing
4.1 Team killing as defined as 'the deliberate and
intentional killing of one's team mates.'
4.2 Team killing is strictly prohibited in DSB.
4.3 If a player is suspected of team killing, the Op on
duty will warn the player three (3) times to stop their
actions.
4.4 If after the third (3rd) warning, the player does not
respond, the Op is authorised to place the player into
spectator-mode, where the rules will be explained to the
player, and release once the Op is satisfied that the
player understands the rule.
4.5 If after release from spectator-mode the player
continues to break rule 4.2, the player will be given one
(1) warning to cease all further actions, and if not
complied with, the Op on duty is authorised to place the
player in spectator-mode where the rules will be explained
again, followed by the players release.
4.6 Rule 4.5 applied.
4.7 If after release from spectator-mode the violator
continues to break rule 4.2, the Op on duty is authorised
to ban the player from the zone for ten (10) minutes.
4.8 Once ten (10) minutes has expired, the violator will
be allowed back into the zone to resume game play.
4.9 If upon returning to the zone the violator breaks rule
4.2, the violator will be given one (1) warning, then
placed into spectator-mode if actions do not cease,.
4.10 Rule 4.7 applied but supplemented with twenty (20)
minutes.
4.11 Rule 4.8 applied but supplemented with twenty (20)
minutes.
4.12 Rule 4.9 applied.
4.13 Rule 4.7 applied but supplemented with thirty (30)
minutes.
4.14 Once the violator has been banned from the zone for
thirty (30) minutes the Op on duty will report the
incident to Senior Staff who will then evaluate the
situation and has the discretion to ban the violator from
the zone for a longer period of time, depending on the
relevant circumstances.
5. Duel Arena
5.1 Players can duel one another by typing ?go duel &
from there the rules against duel interfering apply.
5.2 A player is defined as duel interfering if 'they enter
into an open duel box, which is being utilised by other
players, and in so doing interrupts the duel, when not
invited to participate.'
5.3 The Op on duty has the authority to enforce players
accused of duel interfering.
5.4 Forthwith, the Op on duty shall post an arena message
announcing that all those players who have not been
invited to a duel must cease and leave the duel box.
5.5 If the suspected player continues to duel interfere,
the Op on duty is authorised to warn the player three (3)
times to cease actions.
5.6 If the warned player has not responded the Op on duty
is authorised to lock the player into spectator-mode,
whereby the Op will inform the player of the rules against
duel interfering, and after which time when the Op is
fully satisfied that the player understands, the player
will be freed from spectator-mode to resume game play.
5.7 If after release from spectator-mode the violator
continues to break rule 5.2, the violator will be given
one (1) warning to cease all further actions, and if not
complied with, the Op on duty is authorised to place the
player in spectator-mode where the rules will be explained
again, followed by the players release.
5.8 Rule 5.7 applied.
5.9 Once released from spectator-mode, if the player
continues to break rule 5.2, the Op on duty is authorised
to ban the player from the zone for ten (10) minutes.
5.10 After ten (10) minutes has expired, the violator will
be allowed to enter DSB and resume game play.
5.11 If upon returning the violator continues to break
rule 5.2, rule 5.6 is applied.
5.12 Rule 5.9 applied but supplemented with twenty (20)
minutes.
5.13 Rule 5.10 applied but supplemented with twenty (20)
minutes.
5.14 Rule 5.11 applied.
5.15 Rule 5.9 applied but supplemented with thirty (30)
minutes.
5.16 Once the violator has been banned from the zone for
thirty (30) minutes the Op on duty will report the
incident to Senior Staff who will then evaluate the
situation and has the discretion to ban the violator from
the zone for a longer period of time, depending on the
relevant circumstances.
6. Cheating
6.1 Cheating is strictly prohibited in DSB.
6.2 Cheating is defined as, but not excluded to 'the use
of external programmes, or the like, to gain an advantage
over players, that would not otherwise have been obtained
without the use of such programmes.'
6.3 Lag is not cheating, but if excessive, defined here as
having a ping average above 3750ms, and packet loss above
4.5%. The Op on duty is authorised to place the player,
commonly known as a lagger, into spectator-mode, where the
Op on duty will inform the player and the necessary steps,
if any, to resolve the problem.
6.4 Any player suspected of cheating in DSB, per rule 6.2,
is to be warned one (1) time to cease all actions.
6.5 If the suspected cheater does not cease actions, the
Op on duty is authorised to immediately ban the player
from the zone for sixty (60) minutes.
6.6 After the ban has been executed, the Op on duty shall
report the violator to Senior Staff, whereby, based on the
evidence and pertinent evidence, execute a ban for period
of at least a year (365 days).
6.7 Per rule 6.6, the minimal penalty for cheating is one
year, and depending upon the severity of the situation, a
maximum of five-thousand (5000) days.
7. Bug Exploiters
7.1 Exploiting a bug in DSB is strictly prohibited.
7.2 Bug exploitation is defined as, but not excluded to
'utilising the defects in the Subspace client programme,
or those in any particular arena within DSB, to the
advantage of the exploiter, thereby disadvantaging other
players.'
7.3 Any player suspected of exploiting a bug in DSB is to
be warned one (1) time to cease all actions.
7.4 If the suspected bug exploiter does not cease actions,
the Op on duty is authorised to immediately ban the player
from the zone for sixty (60) minutes.
7.5 After the ban has been executed, the Op on duty shall
report the violator to Senior Staff, whereby, based on the
evidence and pertinent evidence, execute a ban for period
of at least thirty (30) days.
7.6 Per rule 7.5, the minimal penalty for bug exploitation
is thirty (30) days, and depending upon the severity of
the situation, a maximum of five-thousand (5000) days.
8. Language
8.1 Whilst cursing or swearing in not prohibited per
se in DSB, excessive or persistent and constant use of
such words is prohibited.
8.2 The Op on duty is authorised to make an arena message
informing players to refrain from using such language.
8.3 If any particular player does not adhere to rule 8.2,
the Op is authorised to warn the player three (3) times to
cease all actions.
8.4 If the player does not respond to warnings issued by
the Op on duty, the Op is authorised to silence, or as it
is commonly known as 'to gag' the player, whereby the
player is unable to speak for a period not exceeding
thirty (30) minutes.
8.5 If the violator circumvents the Op's authority, i.e.
eludes the silence and continues to use such language, per
rule 8.1, the Op is authorised to warn the player one (1)
time, after which time the player will be banned from DSB
for ten (10) minutes.
8.6 After ten (10) minutes has expired, the violator will
be allowed to enter DSB and resume game play.
8.7 If the violator continues violate rule 8.1, rule shall
8.5 be applied but supplemented with twenty (20) minutes.
8.8 Rule 8.6 applied but supplemented with twenty (20)
minutes.
8.9 Rule 8.7 applied and supplemented with thirty (30)
minutes.
8.10 Once the violator has been banned from the zone for
thirty (30) minutes the Op on duty will report the
incident to Senior Staff who will then evaluate the
situation and has the discretion to ban the violator from
the zone for a longer period of time, depending on the
relevant circumstances.
9. Racism and Sexism
9.1 The use of racially and sexually negative language
is strictly prohibited in DSB, whereby a zero-tolerance
policy is instituted.
9.2 In DSB racism is defined as 'prejudice based on the
expressed belief in superiority of a particular race,
antagonism towards other races, and/or the use of language
which has been objectively determined to be racist in
nature arising from the aforementioned definitions.'
9.3 In DSB sexism is defined as 'prejudice or
discrimination against people, including women, but not
excluding others, because of their sex, or sexual
preference, and/or the use of language which has been
objectively determined to be sexist in nature arising from
the aforementioned definitions.'
9.4 Any player caught in violation of rules 9.2 and 9.3
will be warned three (3) times.
9.5 If after the third (3rd) warning the player has not
stopped the use of such language the player will be
silenced for a period not exceeding sixty (60) minutes.
9.6 If the violator circumvents the Op's authority, i.e.
eludes the silence and continues to use such language, per
rules 9.2 and 9.3, the Op is authorised to warn the player
one (1) time, after which time the player will be banned
from DSB for thirty (60) minutes.
9.7 Once the violator has been banned from the zone for
sixty (60) minutes the Op on duty will report the incident
to Senior Staff who will then evaluate the situation and
has the discretion to ban the violator from the zone for a
longer period of time, depending on the relevant
circumstances.
9.8 In instances of racially and sexually negative
language, Senior Staff have the discretion to impose a ban
of no less than one (1) day, with a maximum of seven (7)
days, though longer in the most severe of cases.
10. Banners, Player Names, and Squad Names
10.1 A banner is defined as the 'representative object
near the players name.'
10.1.1 Any banner which depicts crude, offensive, or
racially and sexually negative, or positive language
content is strictly prohibited.
10.1.2 A player suspected of violating rule 9.1.1, is to
be given three (3) warnings by the Op on duty to either
remove the banner or alter its content.
10.1.3 If a player refuses to either remove or alter the
content of the banner, within a reasonable time, the Op is
authorised to ban the player for sixty (60) minutes.
10.1.4 After sixty (60) minutes has expired, the violator
will be allowed to enter DSB and continue game play.
10.1.5 Once the violator has been banned from the zone for
sixty (60) minutes the Op on duty will report the incident
to Senior Staff who will then evaluate the situation and
has the discretion to ban the violator from the zone for a
longer period of time, depending on the relevant
circumstances.
10.2 A player name, or as it is commonly known as, a nick,
is defined as 'the name of the player.'
10.2.1 Any player name which is deemed to be offensive in
terms of negative or positive racial and sexual words, is
to be given three (3) warnings by the Op on duty to change
the name.
10.2.2 If a player refuses to change the name, the Op is
authorised to ban the player for sixty (60) minutes.
10.2.3 After sixty (60) minutes has expired, the violator
will be allowed to enter DSB and continue game play.
10.2.4 Once the violator has been banned from the zone for
sixty (60) minutes the Op on duty will report the incident
to Senior Staff who will then evaluate the situation and
has the discretion to ban the violator from the zone for a
longer period of time, depending on the relevant
circumstances.
10.3 A squad name is defined as 'that which the player
belongs to, which is ascertained by using the command
?squad, or by viewing the players on the user interface.'
10.3.1 Any squad name which is deemed to be offensive in
terms of negative or positive racial and sexual words, is
to be given three (3) warnings by the Op on duty to change
the name.
10.3.2 If a player refuses to change the squad name, the
Op is authorised to ban the player for sixty (60) minutes.
10.3.3 After sixty (60) minutes has expired, the violator
will be allowed to enter DSB and continue game play.
10.3.4 Once the violator has been banned from the zone for
sixty (60) minutes the Op on duty will report the incident
to Senior Staff who will then evaluate the situation and
has the discretion to ban the violator from the zone for a
longer period of time, depending on the relevant
circumstances.
11. Squad chats
11.1 Squad chats, as with all ';' chats, with
exception to DSB Staff chats and the local zone chat
('DSB', are not moderated chats.
11.2 Squad chats are the sole responsibility of the
captain of the squad, or the person s/he designates to run
the squad.
11.2.1 DSB STAFF incurs no liability or is responsible for
the monitoring of language, tone or content of squad chats
unless otherwise provided below.
11.3 In the event that a player obtains a squad chat,
called a 'chat invader', either surreptitiously, through
misrepresentation, i.e. smurfing, or other means not in
accordance with the honourable principles of practices of
players, members of the squad chat should ask the invader
to leave.
11.4 In the event that the invader does not comply with
the request to leave the chat, members of the squad should
contact a Senior Op or Smod and inform them of the
situation.
11.4.1 Members of the squad should tell the invader that a
member of Senior of DSB Staff has been contacted but this
is not required.
11.5 Provided that rule 11.4 has been done, the Senior
Member of Staff shall discuss the matter with the squad
members, whereby, and if appropriate, that members may
invite to the squad chat the Senior Staff member to tell
that invader to leave the chat; but this is not required.
11.6 If rule 11.5 proves unsuccessful or is futile given
the behaviour and attitude of the invader, a private
consultation may be in order.
11.7 If after all discussions with the invader s/he still
refuses to leave, the Senior Member of Staff may take
appropriate action as necessary.
11.8 Appropriate action as necessary as mentioned in rule
11.7 includes but does not exclude others, banning the
chat invader from the zone for a maximum of seven (7)
days, or what is appropriate given the circumstances.
11.9 Given the nature of chats, if after being banned from
the zone the invader still refuses to leave the chat, the
Senior Member of Staff may take this into account as a
determination as to whether, but not excluding other forms
of action, a) the invader should be banned from the DSB
boards, b) inform Senior League Staff of the matter so
that their League privileges are extinguished, or in the
event of the off-season, the offence being recorded so
that it can apply once the regular season begins; or c) a
combination of both (a) and (b).
11.10 The above rules, as compared to others in this text,
are not exclusive and may not always be strictly complied
with. This is owing to the nature of squad chats and the
circumstances that are involved in any given situation.
12. Miscellaneous
12.1 Where it is deemed necessary to do so, that is,
given the nature of the situation, the above rules may be
varied or altered at any time but only by the active Sysop
or owner of DeathStarBattle or when authorisation by
either of them has been given to a Member of DSB Staff. |
|
| |
|
|
| |
|
|
|
|
|
| |
Top 5 Players By Points |
|
| Player Name |
Total Points |
| Edude |
9,566,072 |
| Hahpoon |
9,295,868 |
| Fly Swatter |
8,984,633 |
| FreeSpirit |
7,811,301 |
| Guardian Force |
7,779,123 |
|
|
|
|
|
|
|
|
|
|
|
|
