Administration code?

Discussion in 'Warbirds International' started by -exec-, Jun 28, 2006.

  1. -exec-

    -exec- FH Consultant

    Joined:
    Jan 29, 2000
    Messages:
    24,690
    Location:
    xUSSR
    here's a russian discussion on the document project.
    http://forum.wbfree.net/forums/showthread.php?t=30037

    below my translation
    _________________________
    definitions

    WarBirds FreeHost (WBFH, FH, FreeHost) - network online-aviasimulator.

    FH Arena - complex of software and hardware solutions, providing illusion of being in virtual game world of FH.

    player - game member registered at FH server.

    colour - conventional playing side at FH arena, distincted by certain colour.

    own, friendly, colormate - any other player having the same colour as the player in the certain time on some FH arena.

    hostile, enemy - any other player having distinct colour from the player in the certain time on some FH arena.

    violator - player commited or currently commining actions listed in prohibited actions list.

    public warning - warning from arena administrator pronounced on any of player's languages or english language via common forum or via 201 (blue) radio channel. player's ignorance about public warning is not considered.

    player's removal from arena - use of .kick command by administrator disconnecting the player from FH arena.

    player's ban - use of .kick command by administrator removing player's access to FH arena.

    developer - a man taking part in FH development, member of developers' mailing list.
    _________________________
    conceptual issues

    0. this code is created and modified only by FH developers. changes are established by developers' quorum. administrators that are develoeprs at the same time possess developer's vote. administrators that are not developers at the same time have advisory votes. opinions of administrators are taken into consideration by developers.

    1. administrator of arena is a player granted special power on FH arenas. in his own activity administrators are guided by this code, developers' advices and directions, and sane reasons. administrators that are developers at the same time are treated as administrators in this code, if other is not specified.

    2.administrators are assigned by suggestions of players, administrators or developers. administrators are dismissed from administrative duties by developers or by recusal.

    3.administrator have rights to use his special powers on FH arenas only by reasons described in list of allowed administrative actions of this code.

    use of special powers by administrator for other reasons is prohibited.

    list of allowed administrative actions:
    ? use of privileged dot-commands for arena tuning
    ? use of 201th channel for administratove purposes
    ? pronouncement of public warnings to violators
    ? removing violators from FH arenas
    ? banning violators from FH arenas
    ? assistance in arena events conducted by developers, scenario or tournament organisators

    4.administrator does not have rights to intentionally or mistakingly use his administrative advantages (special powers) in personal relations with other players, or threat in any form others by possibility of using such powers.

    administrator does not have rights to use his administrative advantages (special powers) for gaining palying advantages over other players.

    subjective opinions of administrators are investigated by administrators quorum (including at leat two developers) in every disputable case.

    5.difficulties amongst administrators must be solved amongst administrators without players partake.

    6.methods of violation provements and means of penalties over violators are listed in the list of prohibited actions, that is obligatory for administrators.

    7.discussions (or disputes, or demand of explications) of players about administrative actions are allowed only in special forum http://forum.wbfree.net/forums/forumdisplay.php?f=54

    ? any player may demand explanation of administrative actions in each certain case related to the very same player, once.
    ? any player may argue administrative actions of one administrator by clearly formulating his (or his group) pretensions, by posting correct poll. it is preferably to apply provements of player's position.
    ? any player may aks for excuses for his prohibited actions, if he considers accusations just. canceling of administrative penalties should be considered by administrators quorum.
    ? administrators mentionned in dispute are oliged to explain their actions or discuss player's pretensions.

    if facts of ignorance of players by administrators, facts of unpersuasive explanations, facts of incorrect accusations/provements, facts of incorrect use of penalties on violators are revealed, or in case of massive compalining about administrative actions, the mentionned administrator's behaviour must be considered by administrators quorum including at least two developers. after consideration adequate actions must be undertaken.

    8.list of prohibited actions is modified by developers quorum after administrator's request. in this case, administrator is obliged to collect players' opinions about every aspect of proposed modification.
    administrators that are developers at the same time have developer's vote.
    besides of that, developers can modify the list without agreeing with administrators, because of technical or organisationsl aspects of FH development. in this case developers must inform administrators about modifications beforehand.

    administrators may not modify the list of prohibited actions.
    _________________________
    list of prohibied actions

    1.use of different (from official) flight model, weapons, game environment.
    detection: modifications of game files or memory modifiers.
    penalty: eternal ban.
    exclusions: beta-testers actually testing new FH versions.

    2.use of spoiled (transparent) cockpits.
    detection: modifications of game files or memory modifiers.
    penalty: public warning upon first fact, ban upon second fact.
    eternal ban upon third fact after first unbanning.
    exclusions: beta-testers actually testing new FH versions.

    3.extraction of information from enemy radar or enemy radio.
    detection: (yet undefined)
    penalty: (yet undefined)

    4.attacking friendly runway, friendly ground structures or friendly ships for cratering respawn/start points or take-off route or other effects.
    detection: one or two tracks
    penalty: public warning upon first case, ban upon second case.
    in case of tracks of two different facts public warning is not obligatory.
     
  2. -exec-

    -exec- FH Consultant

    Joined:
    Jan 29, 2000
    Messages:
    24,690
    Location:
    xUSSR
    sorry for poor translation... this text is relatively long for a tired man...
     
  3. Tzebra

    Tzebra Well-Known Member

    Joined:
    Mar 2, 2005
    Messages:
    510
    Thanks for the effort you have put forth in translating the above.

    It was interesting to read that purposful warping was not a listed issue.
     
  4. -exec-

    -exec- FH Consultant

    Joined:
    Jan 29, 2000
    Messages:
    24,690
    Location:
    xUSSR
    it's a project in development.
    pls add your description of intentional warping.
     
  5. Tzebra

    Tzebra Well-Known Member

    Joined:
    Mar 2, 2005
    Messages:
    510
    My definition of intentional warping is:
    When a player "purposely" induces warp.

    An admin should be able to check this from their side since the players IP is available. A simple trace-route should provide (ms) times on that players connection(s) from start to finish.

    Most players are honest, and will point out those who are in violation (usually with associated tracks). Most warping players are not in violation since it is usually due to a bad connection somewhere along the route; however a consistent bad connection is something to be concerned about (downloading while playing so as to maintain a high (ms) rate in an effort to gain advantage. (warping on purpose).
     
  6. -exec-

    -exec- FH Consultant

    Joined:
    Jan 29, 2000
    Messages:
    24,690
    Location:
    xUSSR
    if admin is telepathist.

    the trouble is to distinct wether someone did it intentionally, or he is under force majeure (bad provider or bad routing).
     
  7. Gunther

    Gunther Well-Known Member

    Joined:
    Sep 5, 2005
    Messages:
    193
    Once, thnx your effort exec to translate that subject for community. :cheers:
     
  8. Tzebra

    Tzebra Well-Known Member

    Joined:
    Mar 2, 2005
    Messages:
    510
    This is where player input is useful, since they will be the first ones to cry foul. More than one crying foul should be looked into usually through .attach if in the arena, or sequester the tracks from the players.