Project Proposal: KZ Global API

By g-Lprecord holder Tournament #1··Announcement

Hey everyone,

 

For the past few months, we've been working on an experiment called KZ Global API, and we're building it because we want to help modernize the scene, bring communities closer together, and give players and server owners features we’ve been missing. If you’re familiar with CS2KZ or CS:GO KZ, this follows the same core idea: runs completed on participating online servers feed into one shared global top.

 

There are many reasons for this, but I believe the current way of recording demos is not up to today’s standard, and people are not so interested in recording LAN demos on empty servers. Nowadays, people spend time playing with friends on online servers, and I believe that is the core of what unites us today. We want to unite the different communities and servers under one global leaderboard, and in the long term, potentially replace the current world-record system with records done on online servers.

 

Before we push this any further, we want to hear what you think, and find out whether server owners would actually want to join. I want to emphasize that this is not a project meant to give control to kreedz.com. It is purely open source: no one owns it, and it is driven by everyone here. The goal is not to replace every server with a generic one. The goal is to keep each server’s uniqueness, while providing a global, shared top so that anyone can record on any participating server and contribute to a shared purpose.

 

How it would work

 

 

For players:

 

  • Play anywhere. Set a time on any approved server and it counts on the global top. Pro and nub stay separate.

  • Live updates and bans. Servers can show the current best time on that top, and update when someone beats it on another server. A ban in the global system carries to the other participating servers. Switching community shouldn't be a way to keep setting times.

  • See your stats and jump data: You'll be able to pull detailed stats about your runs, longjumps, and overall progress across all connected servers.

 

For server owners:

 

  • Keep your server as it is. We aren't asking you to switch to a new KZ mode. You keep your timer, your local top, your maps, your ranks, and your community.

  • Plug in and pull live data: Install a lightweight module to connect your server, and have your plugin reports finished, valid runs while keeping your local records intact. From there, your server can fetch the global top, current map records, global bans, and potentially even optional features like cross-server chat sync.

 

Open source and public data

 

I want to be straightforward about this because it's bound to come up: kreedz.com isn't trying to take over the scene. The entire codebase is open source, so anyone can read it, self-host it, or argue with how it works out in the open. We're happy to cover the servers and storage - since we already maintain a lot of the historical data - but paying for the hosting doesn't mean we own the data or dictate the rules.

 

The API will be public. Anyone can pull records, leaderboards, stats, replay files, and build a site, a Discord bot, or their own top, without asking us. We'll have our own page for the same data, with stats and replays you can watch in the browser. You can build your own as well.

 

The hard part

 

Getting different servers to agree is the real difficulty, and I won't pretend we have it solved.

 

Communities need to stay themselves. If every connected server turns into the same generic KZ server, we've failed. Two runs can only share a board if they mean roughly the same thing, though. Comparable physics, comparable settings, and the same idea of a legit run.

 

It gets messy in the places you already argue about:

 

  • Pause, movable objects, and breakables. Normal on one server, invalid on another.

  • mpbhop, entity reset, and the other mechanical differences.

  • A LAN demo and a time set on a live server are not the same thing.

  • Anti-cheat verification

 

Those differences are real. They won't disappear because someone put them in a config file. So the goal is a shared global top, not a replacement for the world records we have today. Replacing those would be a separate, later step, and honestly the less likely one.

 

None of the rules are decided, and they shouldn't be decided behind closed doors at kreedz.com. A rulebook handed down from here will kill this before it starts. We need server owners, plugin authors, people who care about demos, and people who play, to find a baseline everyone can live with.

 

I also won't claim this is cheat-proof. No online KZ is. It's built around how people actually play, and it can get stricter later, in the open, with people watching.

 

The code is already public:

 

https://github.com/kreedzcom/cs16kz

https://github.com/kreedzcom/kz-global-api

 

A lot of the foundation is already built, but a global top with only two or three servers is just a test. It only holds weight if the 1.6 community actually wants it.

 

What we need from you

 

We aren't asking anyone to install anything, or to change how records work today. We first need you to share your opinion.

 

The form takes about a minute. It's there so we can gather your opinion on this topic. It asks what you think of a global top, what has to match before two times share a board, whether the tops already on servers should be merged, and which features you'd want.

 

[Google Form]

 

Use the comments for anything that doesn't fit a choice. If you think the idea is good or bad, say why!

 

What happens next

 

We'll go through the form and the comments, discuss with you, then potentially talk to the communities that want to join the project. If a few server owners are up for it, we'll start small, on a baseline they can accept, and see how a live global top feels in practice.

 

If the replies say this won't work, or nobody wants in, we'll shelve it. We aren't going to force this on the scene by ourselves. Either way, we're just hoping to help make the scene a better place for everyone!

 

 

Thanks to fxr and GameChaos who participated to the early development of this project.

 

 

g-Lp

Comments

You need to be logged in to post a comment.

17 Nov 2026, 20:14

Looking forward to it!

17 Nov 2026, 20:28

damn it'd be real cool to see this happen

17 Nov 2026, 20:28

I love this! Demo recording is so clunky imo. Feels like only 1.6 kz still do it, most other speedrunning communities does it in a similar way to what ur proposing.

17 Nov 2026, 20:32

It would be interesting at some point to have global ranks with live demo updates for each map we have in common. Possibility to see server top1 pro/nub record on the records page would be enough for the start.

18 Nov 2026, 17:35

Yes, that would definitely be one of the early goal!

17 Nov 2026, 21:46

ambitious, hopefully it will work

18 Nov 2026, 02:26

I've ruminated a similar idea in the past few months but I've come to the conclusion that this isn't worth pursuing. From what I've seen, people like their local, even secluded, but diverse communities where they compete against people they know. Each server has their own flavor of plugins and conventions, and I'd say it's all working pretty well right now. I have a hard time imagining that implementing what you ask wouldn't make every server feel the same. Either that, or the times might not end up on level ground. But this isn't even my main criticism. A global server leaderboard would quickly place itself as a competitor to this community's demo system (which is also a global leaderboard), dividing the best climbers' attention even more than it already is. I don't think it makes sense to maintain two competing systems, and the community would inevitably decide the more convenient one and topple the other. What I'm saying is that a (successful) global server leaderboard would likely kill demo recording, a practice that has worked perfectly well for decades, completely. I can guarantee that demos will keep working 20 years into the future. I can't say the same about any server leaderboard. Our system has a vastly better track record than the leaderboards CSGO or CS2 had/have (nevermind other speedrunning communities that rely on easily fake-able and inscrutable videos). We have complete archives going back decades because we chose to use the demo format as the single source of truth. In contrast, a ton of GOKZ history is gone to the wind. I'm strongly opposed to replacing the demo-based approach with server times before it has been thoroughly demonstrated that they can match the durability, accuracy, decipherability and other strengths of LAN demos. Also, what if you want to beat a world record on LAN with no ping? I think this is a case of a solution looking for a problem. We _could_ do this, but are people really that unsatisfied with the current mode of operation? This is a proportion of historic magnitude. I'd urge you to think carefully about what it could mean to the community, as it essentially asks us to abandon the tried and true way this community has operated for more than 20 years.

18 Nov 2026, 02:58

Support for LAN play is never going to be abandoned, though I see the concerns in regards to segregating the community, or rather, the top players' attention. I also highly doubt we will change the terminology. World Records will be still referring to runs done on LAN, whereas the best times on global tops could simply be dubbed as 'Global Server Record' (GSR), therefore there wouldn't be any overlap and the messaging behind it will be quite clear. Nonetheless, I also think this would raise the activity since casual, and even very good players, could be more motivated to play for a chance to be in the top10 of a particular map, whereas the current system rewards only the WR holders. I do think it's good to take a look at how speedrunning games work, together with, for example, CS:S Surf, which has one of the oldest standing databases (KSF). It's been working wonderfully and still does, with, mind you, a way bigger and active playerbase than 1.6 KZ, even though they are almost just as old. Moreover, they have several playstyles/modes there, yet the activity is pretty much the same and people still have a favourite/main gamemode that's deemed as the most prestigious one. In that sense, I do not think LAN WRs would ever lose their prestige. Also, what happened to GOKZ could have may as well happened to us (since its been explained to me in great detail), it's a really unfortunate situation, but it is not because of their system that they do not have said history anymore. Besides, CS:GO KZ started off without a clear direction, just a bunch of newbies that wanted to have KZ in CS:GO, and then over time more knowledgeable people came in and tried to 'fix' or build upon what was already ther. For instance, the current version of CS2 KZ is still NOT officially released, 3 years later since the game's been out. This is to ensure that the concerns you mentioned about history are to be avoided. In fact, in 10 years, theirs will be even more complete than that of the beginning of 1.6 KZ. Again, I want to emphasize that we have no intentions of abandoning the current demo system and we will even continue to work on it. This is just an alternative way of playing to bring together all communities and players of different levels. Also, keep in mind each community would still have their own local leaderboards, and then they can simply also see the global ones as well. There has to be some basic threshold, but I would say there are already hundreds of maps that are already comparable no matter the server/community. EDIT: One more thing regarding legacy concerns - as far as I understand the system, even if a server is to go down one day, the times and the replays of said server are still going to be preserved in the database and people would be able to watch them.

18 Nov 2026, 17:45

I think you're raising fair points about competing for the global top versus our current system. However, I think the biggest benefit of a global top isn't actually the competition, it’s the stat tracking. Being able to log the maps I've played, hours spent on servers, maybe lj stats, and past runs is great. Historically, having that data tied to specific communities has been a pain because when a server dies, all that history is lost. Nowadays, I almost feel pressured to only play (okay I don't really play much...) on the servers where most of my stats are already tracked. Maybe it's just me, but being able to look back at runs from years ago is a massive incentive to keep playing. Replacing the current world record system entirely might be idealistic, but creating a common platform for everyone’s history feels like a major upgrade, and it doesn't have to ruin what makes individual servers unique. Right now, if a few major communities shut down tomorrow, we’d be left with almost nothing outside of archive sites like kreedz.com or cosy-climbing. I want the whole community, not just the hyper-competitive side of it, to keep living and improve for years to come.

18 Nov 2026, 21:41

As an active jumper who has what it takes to break some wrs, I enjoy playing pubs way more than lan. Communities like kzee already have a built-in browser based record viewer, plus I'm sure it's possible to provide with the demo for each record both server side and client side. There are no issues with watching demos at all. This could actually draw interest of conventional LAN players but I personally don't find it bad or good, and I don't see how it could hard KZ community as a whole. As for niche servers with their own atmosphere, where people rather compete vs each other, the owners can just copy their server and choose not to connect it to the global leaderboard. They can even host their own servers if they really want to at the end of the day. That way they 'd have two servers at once - one with global leaderboard and another without it. And tbh, between the lines, you've basically said it yourself - judging by your logic, this new method is more convenient and jumpers will likely choose it, if I understood you correctly. So I don't really understand what the problem is if it's a more convenient way that more people would prefer. I would actually expect growth in competitve kz playerbase. I also don't understand the fake videos part, I guess I'm missing something, And regarding record tracking, that's also a solvable issue - just add an appropriate tag to clarify if it was made on pub or lan, in case there'll be a united mixed KZ leaderboard. But as it stands rn, there'll be separate leaderboards with, even, different labels: WR and SGR. I agree after so many years it's a big change but honestly I don't see downsides, none of your points coinvinced me and many of them are subject to be solved. With all due respect to the legend Flibo.

19 Nov 2026, 19:40

I believe some "verifications" in other communities involve just recording it with good enough quality and using a handcam pretty much. So faking them is much easier than having a demo recording with a bunch of data inside that can be put through algorithms and manually reviewed.

18 Nov 2026, 05:11

I'm not involved in demo recording or record-setting at all, but it seems to me our servers are quite different from the Chinese segment - with their snap taps, slide saves, and a ton of plugins. The direction from that previous news post about 'A level playing field' is way more interesting.

18 Nov 2026, 05:13

Flibo made some great points; I agree with him. But chorykapitan made the greatest one: 'ambitious'. There are just so many things that could go sideways. So much polishing, fine-tuning, dealing with servers, people, anticheat, and so on and so forth. The list is almost endless. Would love to see it happen one day, but you have a very long road to walk. Good luck to you with this one.

18 Nov 2026, 07:56

It's okay to have global top on the servers that's all. WR's gonna be cheated if you allow this way

18 Nov 2026, 13:28

Kreedz.ee strongly supports the idea of a global server-record leaderboard and would be happy to participate under the following conditions: 1. Independence: Communities retain full control over their servers, plugins, gameplay, and administration. No mandatory software that enforces settings or external decisions. System must allow only one feature to be used: sending data to API, and nothing else. 2. Privacy: Only completed records and necessary verification data are shared. No player-session tracking or unnecessary collection of player activity. Current implementation unfortunately is a spyware that sends all player sessions to API. 3. Existing records: Historical records must be included. Years of competitive achievements shouldn't be left behind simply because a new system is introduced. 4. Compatibility: Integration should not interfere with existing plugins or require replacing established recording, anti-cheat, and gameplay systems. 5. Credibility: We support common competitive standards, transparency, and record verification. Collectively we develop guidelines communities can use to ensure fair environments. Our proposal is simple: Let communities submit their existing and future records directly to one Global API. We're happy to share our configurations, explain our plugins, provide replay evidence, and follow collectively agreed standards. Kreedz.com can verify submissions without controlling participating servers. We believe the current implementation needs to address these concerns before Kreedz.ee can participate. We want to unite existing communities and their records, not start everything from zero under a new centralized system. Hopefully, we can find common ground. We appreciate the work being done on this project and genuinely wish it success!

18 Nov 2026, 18:04

We had some (conflicting) discussions, but here are my thoughts: > 1. Independence: Communities retain full control over their servers, plugins, gameplay, and administration. No mandatory software that enforces settings or external decisions. System must allow only one feature to be used: sending data to API, and nothing else. I think the goal isn't to force anything with this "global API" plugin (or w/e we should call it). It's meant to be bi-directional, servers receive data that they may use or not: get the list top list, information on the players, whether someone is banned, etc. Then there are data that you should send: the runs, whether a player has joined or disconnected from the server, etc. This is used to have a baseline of public live data for the global API system. > 2. Privacy: Only completed records and necessary verification data are shared. No player-session tracking or unnecessary collection of player activity. Current implementation unfortunately is a spyware that sends all player sessions to API. First, everything is open source and public, nothing is meant to be secretly sent over the network, and in any case, most of the events are based on hooks that the server owner needs to implement (in the current version). Then, I think we need a minimum of data to be able to serve useful information: live server info, player info (last time he played, how long), run info (time, replay, cp/gc, etc.), and maybe more. This is all public information that will be available for everyone, and I think it makes the global service more interesting for everyone. > 3. Existing records: Historical records must be included. Years of competitive achievements shouldn't be left behind simply because a new system is introduced. This is a tricky question, because in an ideal world, we want every record to be checked - both through the plugin anti-cheat (yet to be defined) and the backend anti-cheat (post-processing of the run). How do we ensure that existing records are legits, made with correct settings, without cheats or other modifications of the game? > 4. Compatibility: Integration should not interfere with existing plugins or require replacing established recording, anti-cheat, and gameplay systems. For sure, I think the goal is to have our plugin on top of what the server has - it should not require any modification, except if it does not comply with the global rules we have defined (a random invented example: no moving blocks allowed). > 5. Credibility: We support common competitive standards, transparency, and record verification. Collectively we develop guidelines communities can use to ensure fair environments. Of course, this is the goal of this project, everything is meant to be open source and managed by people from different communities. You later mention Kreedz.com as the verifier, but it's not meant to be, really. We are happy to host everything, we are also happy to have someone else trusted to host everything, in which case we would not manage anything. The coding part is open source, only the infrastructure would be private for security reasons (for the hosting owners). The data should be accessible through public endpoint for everyone.

19 Nov 2026, 00:24

> This is a tricky question, because in an ideal world, we want every record to be checked - both through the plugin anti-cheat (yet to be defined) and the backend anti-cheat (post-processing of the run). How do we ensure that existing records are legits, made with correct settings, without cheats or other modifications of the game? I will use this as a way to share with everyone else a potential solution for this problem. But before that, let's talk about the pros and cons of both worlds: 1. Only new records - Pros: All records are verified, there are replays for every single record, and there are anticheat checks for both server settings (e.g. mpbhop, movable objects etc.) as well as regular cheating. - Cons: The playerbase's interest, and especially top players', will be pretty much nonexistent, and for a very long time at that. If times are not competitive, people don't really want to play, especially if they have two alternatives: LAN records or existing local server records. KZMod and Momentum Mod right now are a very good example of this phenomenon. That's why for instance, CS2 KZ will be wiping out all records once the plugin is officially released. 2. Merge with old records - Pros: All players, old and new, will be incentivized to play. It's really that simple, records will be extremely competitive and they'd have weight since there's history behind it. It's the same as releasing a new map in 2026 -> It's always boring to record the first WR because the player knows there's no prestige behind it. Whereas recording a map like av_degyptianez, that has a rich history going back to 2008, is five times more alluring. - Cons: As g-Lp pointed out, many records, and especially very old ones from some of the older communities, have questionable records. It's not even just about having cheated runs, it's about server settings and things like /pause abuse, mpbhops abuse, hook, noclip, checkpoints on slides, breakables, movables and etc. With that being said, I think the best of both worlds would be to have three separate and filterable tops: 1. Verified Records -> All records are verified by the AC and all of them have a replay. 2. Merged Top -> An option to see a mix between verified and non-verified records. 3. Unverified Records -> This one might not seem useful at first, but in reality, any record that fails the AC check can be diasplayed here (for e.g. the AC deems a new run invalid because of a questionable or debatable difference in a mpbhop or w/e other example). All old records will be also part of it. I do believe having this approach would address most of the concerns raised by the both of you.

19 Nov 2026, 00:34

This approach of having verified, unverified, and a merged category is a great idea. I think this would also open the gates for other communities who have different physics or rules to still integrate their records if they want, they'll just be unverified (or introduce a tag for each communities rulings?). Filters can be made for communities and verified/unverified. I also think making a clear distinction between new/old records with another visible tag could incentivise people to beat the old records, hoping to see "new" next to them. It can become a goal to get all records to say "new" maybe? And, if you still have the demos from old records, you could just wait for people to look at it and remove it or verify it based on if values are found to be accurate or not right? If it's discovered that a run uses pause abuse, just remove it because it's not legit. Doesn't seem that complicated to me but I'm ignorant.

19 Nov 2026, 00:56

i think, from what i've understood, that this is a pretty good compromise overall, especially since starting from zero would make it difficult to attract players when there's already so much competitive history behind existing records, and preserving that history while establishing a new standardized competitive environment seems like the most reasonable approach n i agree that an entirely fresh leaderboard would probably struggle to generate the same interest as one with years of competition behind it my main concern is grouping historical records together with records that fail anti-cheat checks, because there's a significant difference between a record that simply lacks sufficient evidence for verification, one that's rejected because of incompatible server settings, and one that's actually flagged for cheating. i don't think these should share the same classification, since doing so could unfairly undermine the credibility of legitimate historical achievements. a failed verification shouldn't necessarily imply cheating either especially when we're still figuring out which gameplay differences should be acceptable there's also the question (as far as I understood)of which leaderboard would actually be considered authoritative. if the merged top contains faster historical times, would someone setting the fastest verified time still be considered the global sr holder? which record would participating servers display, announce, or use for their replay bots? i think this distinction needs to be established early, otherwise we risk creating multiple competing interpretations of what a "global record" actually means. personally, i'd see the merged top primarily as a historical comparison rather than the authoritative competitive leaderboard another thing worth considering is retrospective verification, i.e. if an older record has an available demo, documented settings, and sufficient evidence of legitimacy, i don't see why it couldn't eventually qualify for the verified leaderboard. otherwise, the verified top still starts completely empty, meaning the three-leaderboard approach doesn't entirely solve the problem you're describing in my eyes, and allowing historical records to earn verified status could provide some immediate competition without automatically accepting everything i also think we need to be careful about treating all historical records as directly comparable, obviously different communities have historically allowed different things regarding pauses, mpbhops, movable objects, breakables, checkpoints, and other mechanics, therefore a record could be perfectly legitimate under its original community's rules while not complying with the eventual global api standard. simply merging those times doesn't resolve their incompatibility, i think we should preserve information about where records originated and which rules they were recorded under, so players can understand what they're actually comparing that also raises the question of how historical records would be imported in the first place, who decides which communities' records are trustworthy enough to include, particularly if some have extensive replay evidence and others have very little? i think we'd need some transparent, collectively agreed criteria rather than relying solely on the reputation of individual communities, otherwise, we're potentially replacing disagreements about individual records with disagreements about which communities deserve recognition. one more concern is treating verification as a permanent "yes or no" decision. anti-cheat systems aren't infallible, and as detection methods improve, previously accepted records might turn out to be questionable, while rejected ones might eventually be cleared. i think records should retain their verification history and have some kind of review or appeal process, rather than automatically moving into an unverified leaderboard whenever a check fails, and maybe confirmed invalid records shouldn't be competitively ranked at all? overall, i really like the idea of having separate verified, historical, and combined leaderboards. i'd just argue that verification status, ruleset compatibility, and actual evidence of cheating should be treated as separate things. perhaps instead of treating every record as simply verified or unverified, we could distinguish between verified, legacy, pending review, incompatible, and confirmed invalid records, while still presenting them through the three leaderboard views you've suggested? that way, we're not throwing away nearly two decades of history, but we're also not sacrificing the credibility of the new global system just to make its leaderboards populated from day one

19 Nov 2026, 19:48

Very true, would the demo-recording leaderboard remain the point of "truth" and the server records is just for side-tracking for "possible runs" that gets updated in real-time? I think there is an element of how the community would view the global top too. If people suddenly decide that it becomes on the same level as the demo recording then that's a problem I think. The world records verified on lan from demo's are *the* world records. The global tops can be used as a reference more-or-less. I kinda figured cheated/invalid runs wouldn't be on any leaderboard... if it's invalid, then it shouldn't be a reference at all (depends on what is invalid though I guess?). I think the solution here is to just have separate section on each map page that has both a global top and verified demo recording as records. You could use the global as a reference for what to aim for when recording the map if you wanted to get the world record. On the other side, if nobody cares to record it, it'll just live as a global top time.

18 Nov 2026, 14:04

This would be pretty massive if South-America, China, Korea, Europe all got a global pro15 leaderboard. The battles for global sr would be huge if it also got discord server-record tab and used ranking system like kreedz.ee uses. The only reason I still play this game is because of the existence of kreedz.ee otherwise I couldn't care less for this game lol. This would bring back people after taking a break and maybe even from complete retirement just to check things out from time to time

18 Nov 2026, 17:47

I agree!

18 Nov 2026, 14:10

hard , but the result is gonna be insanely cool

18 Nov 2026, 15:18

Best news of the year!

18 Nov 2026, 18:29

how could people from North/South America - OCE they could do public world records with 300ms due server issues? [lack of servers mostly] is kreedz.com willing to provide server to this regions so they can play/"record"?

18 Nov 2026, 18:33

kreedz.com does not provide any server, we just help build and organize (and potentially host) this global solution. It's still up to any server to use the plugin and be involved, for now we don't have plan to host any servers.

18 Nov 2026, 18:43

I played on EU servers (I'm NA) for a long time on CS:GO and obviously now on 1.6. Having 300ms is quite high, I see around 150 at most if my internet doesn't decide to doodoo itself, and it's mostly fine for me. The bigger issues are with plugin-implemented physics alterations (like CJ on CSGO) or boost pads in maps. They can be done depending on how bad ping is, but I don't think it's a major issue for people who can get even ~100ms. Maybe I'm just used to playing with high ping though.

18 Nov 2026, 18:36

In theory, this is a good idea. There are issues that have become apparent when relating to CS:GO however. # Ban System / "Global" Bans On CS:GO, if you were "global" banned, it prevented you from playing most servers. GOKZ solved this by allowing server owners to optionally allow global banned players to play without being able to submit records. I don't see this being a major issue on 1.6 because the physics are not created via plugins but rather are 1.6 engine physics themselves; you can just play on LAN. The real punishment from being "globally banned" in this system is no longer being capable of playing on servers with friends, and using a server's features to your advantage. You are not locked out from enjoying what KZ is. # Anti-Cheat This system also introduces the capability of a proper Anti-Cheat plugin that all servers can run. Breaching certain thresholds with FOGs could be grounds for kicking or banning someone depending on how plausible it is. Yes, false bans can and will occur, and I believe taking the "innocent until proven guilty" here is very important. CS:GO's global system has false banned top-players who are known to not be cheating because of edge-cases in the code. They were unbanned in time, but what happens if it wasn't a trusted top player, but a random? # Adminstration When it comes to the administration on CS:GO's global system, it sucked. I have multiple friends who were banned unjustifiably according to the Global Team's own rules on banning. I won't get into any specifics here, but if you want to know DM me on discord. With this in mind, who will be administrating bans? On CS:GO (from my knowledge), it was a small select few, and dwindled over time to mostly being only one. If one person is the central manager of bans, it becomes too easy to do whatever they want. I think all contributors or "stakeholders" as g-Lp put it should be apart of a larger ban or unban decision. Yes, I know this can be taxing with the amount of cheaters, but this is something you would be signing up for by creating this. Maybe look into getting more demo checkers/ban managers? If someone wasn't cheating and truly wanted to be unbanned, I would imagine they would submit a ban-appeal. I have my own story regarding being global banned on CS:GO since December 2018 permanently. It was a valid perm-ban according to the rules. I have my own excuses I could get into but it's irrelevant to this. The issue I have is that I went for many years playing legit on non-global servers and still, was never given a second chance. I gave up caring and continued playing however I could because I enjoyed KZ. This is an oversimplification of my case, and I might be under-playing my childish attitude towards the whole situation, I was ~13 years old when I was banned for some context, but to *never* offer a second chance after years? # The chance of Discrimination. On CS:GO, being global-banned immediately caused you to be considered a hard-core cheater and to never be trusted, they really took the "once a cheater, always a cheater" mentality at face value and condemned anyone who was global banned. It became a slur or demeaning term of to diminish accomplishments or any sort of reputation one might have. The words: "nope, you're global banned" was all it took for the elitist of the system to not care about anything you do KZ related. I fear that people who get global banned, will have all their interest in KZ voided due to flying too close to the sun, like I did. In the long-term, this hurts this community due to the minimal amount of players. People make mistakes, let them own it by serving a sentence and be allowed to come back at a later date. They can still play on LAN, just won't get recognition. There are many cases in different game communities of redemption stories happening. For example, look at SpaceUK, Andromeda, and Noobas from Geometry Dash or Flaven and Cloutiful from osu! It's possible for people to change (these are ones I know because I've been apart of these communities). # Final Notes Doing something like this will be challenging, and would require more personnel to operate most likely. Second-hand opinions suggest that part of the reason CS:GO Global sucks is because of a lack of people. They created a central power for kreedz, it became popular, they lost to corruption and the issues that came with operating the system, and it became a shitshow. I do believe this is something that can help bridge a gap, but it should stay optional and designed in a way that does not remove the contributions of other communities. The final, FINAL thing I will say, if anyone with power does something that people find issue with, playing favoritism towards them will be the downfall. Select the owners and administrators carefully. P.S. I would choose something better than "Global". Since you plan on making it open-source, OpenKZ? It's an "open" API... maybe?

19 Nov 2026, 03:16

wow ure so smart and cute

19 Nov 2026, 19:36

<3💕<3

18 Nov 2026, 19:13

1. Each server keeps its own style, and a valid run can also count on one shared top. What do you think? If style implies server plugin (commands that a client sends to a server), then I think every server must be allowed to keep whatever they like. BUT! A personal experience and recommendation from me to the server owners: guys, try to stick with common commands - /uqsounds is an easier way to disable aanoying sounds than having to go to /settings and waste time to find the right option, or trying to figure out the proper command to type in chat. If "beoming the same" means having same server options and their style (NV modes, live timer comparisons, time press sounds and all that), then I think, again, let everyone use whatever they like, just don't add any unnecessary sounds by default, the lesser the sounds on the server, is the best. As to the servers looking the same doesn't faze me at all, as long as it's something like kz.ee, rather than kz.bg with a bunch of unnecessary sounds and hud (sorry, no personal feelings and respect to the owners <3). 2. Before two times share a board, what has to match? Physics and server settings - I'm not quite sure what's meant here by physics. 10/100aa should be optional choice. Internet packets settings such as rate and all that stuff shouldn't matter because it's allowed by the game by default. Or am I missing something? The same pause rules - Idk how pause rules differ on servers, I thought you can open doors in pause on all servers no? The same rules for movable objects and breakables - absuletely yes, since it directly affect times. If my memory doesn't fail me I remember some server to have had it so that bhop blocks would only go down for you only, if you hit the trigger. As for the doors being open, the server must either force abuse, make them always open, or best - have it to work differently personally for each player. Can't think of more potential issues with movable objects, but breakables doesn't seem like a problem to me. The main idea regarding both is every that share the top must use same conditions in that sense. Some shared check against cheats - in perfect case scenario all the cheat cases must be shared between heads (and/or AC developers) of all servers, and decisions must be made collectively. For obvious reasons not every developer might want to share their anticheat, even it's narrow range of communities heads, but I'd still like to believe only the trusted group of people would be involved and all would have the opportunity to have access for method details of every part. If the idea of sharing methods not working out, then I guess leave it for decision of a responsible admin and the entry is not furtherly moving into the globabl leaderboard, I don't have a better decision rn. What's your take? 3. Pause, movable objects, and breakables on a global run. I answered above, but options such as "Allowed when that server already allows them" and "Depends on the map" must not be taken into consideration because both entail injustice and confusion when it goes to global leaderboards. 4. The tops that already exist on servers. Should they be merged into the global top? On paper, of course YES. Main worry is whether all entries across all global servers were made under the same conditions, pitfully the answer is NO. What I suggest is handpick all the questionable maps, keep the leaderboard for the local top (if wish so), but ban from the global leaderboard. Once that's done, such maps must be standadized for all global servers. Aand I just realized it's basically "Only the times that would pass the same rules.", so ye this option. 5. A global top is the first step. Replacing today's world records would be a later one. What do you think? Global and LAN should both be standalone, one does not conflict with the other. Glad to see this idea is getting in the work <3

19 Nov 2026, 00:25

What if we named it WAN 🫢

19 Nov 2026, 12:51

WAN? 🤔

19 Nov 2026, 00:49

What about introducing rulesets? The idea is taken from Geometry Dash where different "lists" have different rules on what they consider "valid". The core idea would rely on just adding tags to runs as to what "ruleset" (what server the record came from I guess?) was followed. The Kreedz.com page could link to or describe each communities' rulesets and how they differ from each other. I think it opens the doors for every community to integrate regardless of their own rulings on what is a valid run or not. You would have your own "official" ruleset.

19 Nov 2026, 03:16

good take lol ure so awesome

19 Nov 2026, 05:33

Here's my 2 (hundred) cents as the main CS2KZ plugin dev: I saw concerns about the new global leaderboard competing with the existing demo-based system. If I understand correctly, this proposal isn't necessarily adversarial to the current system, but rather something that complements it. From my experience with CS:GO KZ, the "LAN" way of doing runs will never truly disappear, especially at the top level. Server latency will always be a disadvantage for top players, and those who want to grind the same map repeatedly will still prefer LAN. CS:GO KZ doesn't have true LAN, but whitelisted/private servers effectively serve the same purpose. More importantly, a unified API isn't primarily about improving legitimacy. It's about scale and accessibility, allowing players to track their progression across servers over time, which is appealing to casual players like me. Yes, the risk of server owners faking records is there, but from what I've seen in CS:GO/CS2, server owners generally have little incentive to do so. They want their players to compete globally, and keeping the leaderboard clean is in their own interest. Bugged runs or problematic servers can simply be removed from the API when necessary. Individual cheaters are another concern. In CS2, every run is recorded in a replay file and submitted to the API, allowing anyone to inspect suspicious runs. Replays help us identify the cause, fix affected records, and contact server owners. If they refuse to resolve the issue, their servers can be removed from the API. In my opinion, the bigger risk is the API becoming a single point of failure. This is particularly problematic in CS:GO, where demo verification isn't an alternative. If the API goes on fire, people may lose their reason to play (ie. "it doesn't count anyway"). On the other hand, a global API also preserves records even when individual servers shut down. Another consideration is prestige. In CS:GO, global records are generally much more prestigious than individual server records, with a few exceptions. Introducing this system to 1.6 might inevitably change what players consider prestigious. That said, a global leaderboard is already a thing in 1.6, so perhaps this concern is somewhat overstated. There's also the question of movement consistency. From what I understand, not all 1.6 servers necessarily use identical settings, despite supposedly running stock movement. Server owners will need to agree on a common standard before this proposal can work. This isn't much of an issue in my CS2KZ plugin, where movement is either custom (with me acting as a dictator setting the rules) or fully stock (with Valve being the dictator instead). 1.6 also has an unique issue with movable blocks and other features that aren't multiplayer-friendly. CS:GO/CS2 maps are almost always designed with multiplayer in mind, but not 1.6, so this is something that needs special consideration there. API administration is another potential concern. Having someone in charge creates opportunities for abuse. In CS:GO/CS2, it's more like a janitor's work, historically speaking. Transparency through public admin-action logs and restricting sensitive access to trusted people who actually need it seem like reasonable safeguards. Can always just fork the API in the worst case scenario. Regarding record preservation, I'd suggest keeping all runs with demos and classifying the rest as "unverified" (different flavors of it of course, to distinguish old records from, say, 2010, from suspicious runs submitted minutes ago). CS2KZ will wipe all records on release day mostly because movement code has changed significantly over the years (which isn't the case for 1.6) Player privacy is more complicated. More data can help establish legitimacy and detect cheating, but there needs to be a reasonable limit. In CS2, most servers already broadcast player information through the A2S protocol, so tracking active players through the API seems reasonable to us. I disagree with the concern that every server will start feeling the same with an unified API. After 10+ years of playing CS:GO KZ across servers worldwide, I've rarely experienced two servers feeling identical. Plugins, map voting systems, community features, and especially the players themselves make each server unique, even when the gameplay is the same. Regarding bans, permanent bans in CS:GO seem rather silly in hindsight. That doesn't need to be repeated here. Record wipe + a reasonably long ban should be sufficient. A global ruleset could define standard punishments while allowing individual server owners to decide how strictly they enforce global bans. Regional/country leaderboards could also be interesting. I'm not sure how they would work, but I'd love to see them someday. And if this proposal succeeds, perhaps one day we'll even have a single API for KZ statistics across every CS version. But I'm getting ahead of myself here.