KZ-Climb

KZ Climb Community Website

Sep
23
https://github.com/klyve/KZTimerGlobal/releases/download/1.8.5/KZTimerGlobal_1.8.5.zip

Changelog:

· Removed convar "sv_timebetweenducks"

· Switched global db from IP to static address.

· Preparing for Global API

With this release Klyve has begun to improve the KZTimer build process. As we get closer to the release of KZTimer 2.0 there will be many changes happening both within the game environment, with the plugin, and the community as a whole.

The first big change will be the the new GitHub Repository; switched github from https://github.com/1NutWunDeR/KZTimerOffical to https://github.com/klyve/KZTimerGlobal

This will allow us to keep better track of the development of KZTimer. There will be a few changes to KZTimer coming in the next few days including a Global API.

Another change is the transition from the old “Kreedz Europe” group that was from 1nuts management of KZTimer to the new group more appropriately named as “KZTimer Official”.
It can be found at: http://steamcommunity.com/groups/KZTimerOfficial

This will begin a greater transition for the community that will better represent the current leaders of KZTimer and the community. I hope to see everyone stick with KZ through this exciting time.

Thanks,

Sachburger and the rest of the Global Admin Team
Sep
13
Hello KZ Community,

Our strategic focus is to identify and ban anyone who attempts to use unauthorized assistance during a global run. The global ban list has been our effort to maintain a cheating-free™* environment in KZ. However, the current ban list contains cheaters who have used a wide array of offenses - from simple hyperscrolling to complex injected kz cheats.

Today we will be implementing ban durations for different offenses. This will help distinguish between cheaters who deserve a second chance and the more serious cheaters who have clicked their last clicks. Here is how we will be processing these bans:

LJ Cheats
  • First offence:
    • 3 Months
  • Second offence
    • Permanent
Bhop Cheats
  • AHK or Hyperscroll
    • First offence:
      • 1 Months
    • Second offence
      • Permanent
  • Injected
    • Permanent
As a result of this new policy, we will be unbanning 1,442 users today - 1,314 Bhop AHK cheaters and 128 LJ cheaters.

Thank you,

KZ Global Team
Aug
29
Maps removed from globals:
kz_420b (bind sc) kz_420b was actually not bugged, a player exploited times on the map and has been appropriately punished. Please refrain from exploiting KZTimer for cheated global times.
kz_bridge17_v3 (see comments)

kz_quadrant is re-approved (cleared some bugged times), also cleared some old bugged times on kz_symbiosis_final.

EDIT: kz_ziggurath is now kz_ziggurath_fix, all times have been wiped due to a booster exploit.

Mapcycle for server owners: http://pastebin.com/2aif9cUy
Aug
25
kz_freezingridge_go_fix_v4 has been removed from globals due to another surf sc being discovered.
Aug
16
Hello KZ’ers,

We’re excited to announce a new part of the KZTimer Global infrastructure - demo reviews! For those of you with 1.6 history, this will be very familiar to you.

We have created an early version of a demo review tool that allows us to look at the replay bot records that are saved by KZTimer and check them for data that is consistent with cheating. Global times must still be performed on globally whitelisted servers, but we will now have an extra tool in place to verify them. Our freshly-minted demo team that will handle the demo reviews consists of Klyve, Chuckles, Funk, Plekz and Zpamm. The team has a breadth of experience that includes plugin development, mouse detecting, 1.6 experience and general KZ experience.

We welcome any server owners to submit their demos to us so that we can check for cheaters. While we learn how to recognize different cheated behavior, every additional demo that is sent to us will help. If you are suspicious of a player or run, get in touch with the server owner and ask them to send us the demo file.

Using this tool, we have already been successful in identifying our first suspects. There is evidence beyond a reasonable doubt that a player with a number of top 20 times has used injected cheats on multiple runs - including a global pro record. As a result, he is now banned from KZTimer and all of his records have been removed.

We see this new tool as a great refinement to CS:GO KZ and we will continually strive to improve the KZ experience for all users going forward.

Thank you,
KZ-Timer Team
Jul
31
So, as some of you may have noticed, the global database took a hit.
Someone with access to the database decided to delete all the times. This triggered an auto restore from the server to a point at the end of April.
Let me note that all global records have been restored, however top 20 times and bans from the past 6 days were lost. If anything is out of order please contact one of the database admins and they will fix it.

Going forward, we have made sure this wont happen again. A security threat still exists and solving this will render all servers without global access until applied for again. At this point in time, we are looking for other solutions. More information to come.

Sincerely Klyve
Jun
28
New global maps:
kz_cratespeed
kz_cyb_adrenaline
kz_ephemeral
kz_rockjungle

EDIT:
kz_rockjungle is now kz_rockjungle_v2

A small unintended skip was discovered and used by 2 players, offending times have been removed and old times have been transferred.
kz_gfy_limit is now re-approved

Mapcycle for server owners: http://pastebin.com/JxupD5Ta
Jun
21
KZTimer Global Player Rules (This includes but is not limited to)
  1. Cheating
    • Mouse features (MSL, hyperscrolling, etc.)
    • Macros
    • Scripts
    • AutoHotKey or any scripting language designed to mimic or reproduce peripheral input
    • Injected hacks
    • Binds that give an unfair advantage (e.g. null binds or LJ bind, cannot confirm/deny implementation of a check for these binds (and thereby the veracity of this rule) until the release of KZTimer 2.0.)
  2. Exploiting to gain Global times
    • Exploiting KZTimer
    • Exploiting server privilege
The above rules apply regardless of the server being Global or non-Global.

Punishment for breaking the Player Rules of Conduct

If you are caught breaking either of these rules you will be banned. You are however free to appeal this (appeal here), and if you come clean you may be given a chance to redeem yourself, all your records and stats will be wiped. If you proceed to break the rules you will be given a permanent ban and your ban appeal will be denied outright.

Playing on alternate accounts while globally banned:

You are not allowed to return to global servers on alternate accounts while globally banned.

KZTimer Global Server Owner Rules of Conduct

1. Plugins that give players unfair advantages

This includes but is not limited to plugins like hook, flying, teleportation, speed manipulation.

2. Cheating times
This includes using your access to the global database to cheat and insert false times.

3. Hiding or removing bots of global records
Until we get a way to share global bots, any attempt to remove bots or hide a global record from the other players will be considered as breaking rule No. 2

4. Banning or unbanning people from the global banlist

5. Keep your server clean
You as a global KZTimer server owner have a responsibility to keep your server clean. That means reporting in cheaters or cheated times. Your admins are an extension of yourself, so consider them as one. They are as responsible for the server as you are.

Failure to meet these requirements
If you somehow fail to meet there requirements your server will be given a punishment. Depending on the severity of the offence this can include:

  • Strike on the server ( 2 strikes & you're out)
  • Server removed from the global list
  • Global ban issued to server owner