Welcome, Guest. Please login or register.
Did you miss your activation email?
November 29, 2021, 08:19:55 am

Login with username, password and session length
Search:     Advanced search
Savage: XR is a new patch for Savage, created by the Newerth.com staff. The XR1.1 Client is out now! Download it now!
190128 Posts in 11016 Topics by 18631 Members
Latest Member: pesecarte
* Home Forum Wiki Help Search Login Register
+  Newerth Forums
|-+  Newerth Hosted Competitions
| |-+  Newerth Savage League (NSL)
| | |-+  Disputes
| | | |-+  NSL 7: Dispute process
0 Members and 1 Guest are viewing this topic. « previous next »
Pages: [1] Go Down Print
Author Topic: NSL 7: Dispute process  (Read 3712 times)
Quack or die!
Newerth Council
Super Hero Member
Posts: 1083

View Profile WWW
« on: March 04, 2016, 04:49:47 pm »

Before continuing to read this topic, make sure that you have read and understood the following topic:
NSL 7: Rules

A dispute has to be filed as a new topic in the Disputes section.

A dispute can only be filed by a clan/ team-representative, of a clan/team who is participating in the NSL 7.
The dispute has to include the following information:
  • Which party (team/ clan) is accused of breaking the NSL 7 Rules?
  • In which way did the accused party break the NSL 7 Rules? Which specific NSL 7 Rules have been broken?
  • As much detailed information/ evidence as possible (e.g. at which date/ time did the match take place, game-time the incident happenend, affected players, screenhots, demos).

Gridfon, the NSL 7 dispute admin, will go through the filed dispute and will judge accordingly after taking into account the offered evidence and the server demos provided by the server owners.

« Last Edit: March 29, 2016, 09:57:42 pm by valli » Logged

He who controls the past commands the future, He who commands the future, conquers the past.
Pages: [1] Go Up Print 
« previous next »
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2006-2007, Simple Machines Valid XHTML 1.0! Valid CSS!
Page created in 0.014 seconds with 20 queries.