[{"data":1,"prerenderedAt":230},["ShallowReactive",2],{"roadmap":3,"\u002Froadmap":15},{"id":4,"title":5,"body":6,"description":7,"extension":8,"meta":9,"navigation":10,"path":11,"seo":12,"stem":13,"__hash__":14},"roadmap\u002F2.roadmap.yml","Roadmap",null,"Track the our next updates and improvements.","yml",{},true,"\u002Froadmap",{"title":5,"description":7},"2.roadmap","aVp61vg6iM_n5Sn5xrl_s_8Z48Owv-_p933MZk8oWBw",[16,135],{"id":17,"title":18,"body":19,"date":125,"description":126,"extension":127,"image":6,"meta":128,"navigation":10,"path":131,"seo":132,"stem":133,"__hash__":134},"versions\u002F2.roadmap\u002F1.launch-statustw-20.md","status.tw 2.0 is coming 👀",{"type":20,"value":21,"toc":118},"minimark",[22,25,29,32,35,38,41,44,49,52,55,58,80,83,87,90,93,96,99,103,106,109,112,115],[23,24],"hr",{},[26,27,28],"p",{},"status.tw has been around for quite a while. Long enough for parts of it to become outdated, awkward to maintain and, in some cases, held together by good intentions and questionable technical decisions.",[26,30,31],{},"So instead of continuing to paint over the cracks, we decided to rebuild the whole thing. 🔨",[26,33,34],{},"status.tw 2.0 comes with a completely reworked frontend and backend. We have cleaned up old systems, modernized the technical foundation and improved how we develop and review changes internally. That includes better automated testing, more consistent code reviews and processes that should make it considerably easier for us to ship updates without accidentally setting something else on fire.",[26,36,37],{},"The website itself is getting a major visual overhaul. Server lists, player pages, statistics and history views will present their information more clearly, with better structure and fewer walls of unexplained numbers.",[26,39,40],{},"Almost every relevant view will receive live updates. If a player joins a server, a map changes or new data becomes available, you should no longer need to hammer the refresh button like it personally offended you. ⚡",[26,42,43],{},"Server and player histories will also load gradually instead of trying to fetch an unreasonable amount of data at once. This should make larger histories much smoother to browse.",[45,46,48],"h2",{"id":47},"more-for-server-owners-️","More for server owners 🛠️",[26,50,51],{},"The Server Manager is receiving more than just a fresh coat of paint.",[26,53,54],{},"Server verification will be easier to understand and provide live feedback while you complete the required steps. Once verified, server owners can continue adding custom information such as a description, website and Discord invite to their public server pages.",[26,56,57],{},"There will also be several new insights, including:",[59,60,61,65,68,71,74,77],"ul",{},[62,63,64],"li",{},"Your server’s global ranking and performance compared with other servers",[62,66,67],{},"Regular, returning and daily players",[62,69,70],{},"New players and players who stopped returning",[62,72,73],{},"The most active countries and clans on your server",[62,75,76],{},"Map performance and direct comparisons between your maps",[62,78,79],{},"Player-count charts, activity heatmaps and server history",[26,81,82],{},"The idea is simple: server owners should be able to understand what is happening on their servers without maintaining their own analytics stack or consulting three spreadsheets and a crystal ball. 🔮",[45,84,86],{"id":85},"a-much-better-api","A much better API",[26,88,89],{},"Developers will get new endpoints for server rankings, player statistics, activity heatmaps, countries and daily global statistics.",[26,91,92],{},"Server and player responses will also contain more useful information. Depending on what a server provides, this can include map hashes, map sizes, country information, skin colors and an estimated bot indicator.",[26,94,95],{},"We are also introducing API tokens, usage statistics and request logs. Tokens will not become mandatory immediately when 2.0 launches. Developers will have time to create one and update their applications before we begin requiring authentication.",[26,97,98],{},"The API documentation has been rewritten as well. Every route and field should properly explain what it contains, where the data comes from and any limitations you need to know about. “Here is a field, good luck guessing what it means” is not documentation.",[45,100,102],{"id":101},"less-silence-more-updates","Less silence, more updates 📣",[26,104,105],{},"We also know that our communication around status.tw has been practically nonexistent for a long time.",[26,107,108],{},"That is changing.",[26,110,111],{},"We want to use the teeworlds.dev blog and Discord to share updates, explain changes and let interested users know what we are working on. Nobody should have to discover a new feature by randomly clicking around the website six weeks after it was released.",[26,113,114],{},"There are still a few things left to finish, and the final list may grow before release. But status.tw 2.0 is actively being worked on and is getting closer.",[26,116,117],{},"Same status.tw. Much better foundation. Considerably fewer questionable corners.",{"title":119,"searchDepth":120,"depth":120,"links":121},"",2,[122,123,124],{"id":47,"depth":120,"text":48},{"id":85,"depth":120,"text":86},{"id":101,"depth":120,"text":102},"2026-08-01","We are rebuilding status.tw from the ground up with a new frontend, a modern backend and a lot more useful data.","md",{"status":129,"project":130},"in-progress","status.tw","\u002Froadmap\u002Flaunch-statustw-20",{"title":18,"description":126},"2.roadmap\u002F1.launch-statustw-20","EmmAf_Hf4DlYLMZsFXUsniIivfRWaeX_eEi6vdGFQJY",{"id":136,"title":137,"body":138,"date":222,"description":223,"extension":127,"image":6,"meta":224,"navigation":10,"path":226,"seo":227,"stem":228,"__hash__":229},"versions\u002F2.roadmap\u002F2.launch-statustw-pages.md","Your server deserves its own status page 🌐",{"type":20,"value":139,"toc":218},[140,142,145,148,151,154,157,163,166,170,173,176,196,199,202,206,209,212,215],[23,141],{},[26,143,144],{},"Finding a Teeworlds server is easy enough when you already know its address.",[26,146,147],{},"Presenting an entire community properly is a different story.",[26,149,150],{},"Many communities operate several servers, have their own Discord, website and branding, and want one place where players can quickly see what is currently online. Sending someone a collection of IP addresses in a Discord message technically works, but we can probably aim a little higher than that. 😅",[26,152,153],{},"That is why we are planning custom public status pages for server owners.",[26,155,156],{},"A status page will let you collect the servers you manage in one place and share them through a dedicated subdomain, such as:",[26,158,159],{},[160,161,162],"code",{},"yourcommunity.teeworlds.site",[26,164,165],{},"Visitors will be able to see whether your servers are online, how many players are connected, which maps are running and other useful live information without searching through the full global server list.",[45,167,169],{"id":168},"one-home-for-your-community","One home for your community",[26,171,172],{},"The page should also make room for the information surrounding your servers.",[26,174,175],{},"We want server owners to be able to add things such as:",[59,177,178,181,184,187,190,193],{},[62,179,180],{},"A community name and description",[62,182,183],{},"Discord and website links",[62,185,186],{},"Multiple verified Teeworlds servers",[62,188,189],{},"Live player counts and server states",[62,191,192],{},"Maps, game types and connection information",[62,194,195],{},"Basic visual customization",[26,197,198],{},"The goal is not to build another complicated website builder where choosing a background color requires watching a 40-minute tutorial.",[26,200,201],{},"It should be quick to configure, easy to share and useful even if your “network” consists of one lovingly maintained server running a strangely specific game type that twelve people refuse to stop playing. ❤️",[45,203,205],{"id":204},"built-on-live-statustw-data","Built on live status.tw data",[26,207,208],{},"Because these pages will use status.tw data, server information can update automatically. Server owners will not need to maintain the same details in several different places or manually change the page whenever a map rotates.",[26,210,211],{},"We are also considering how status pages could work with existing status.tw features such as server verification, custom fields, statistics and webhooks.",[26,213,214],{},"This feature is still in the planning stage, so the final design and exact customization options are not locked in yet. We would rather keep the first version focused and useful than turn it into a giant page builder before anyone has even used it.",[26,216,217],{},"But the direction is clear: every Teeworlds community should have an easy way to present its servers without building and hosting an entire website from scratch. 🚀",{"title":119,"searchDepth":120,"depth":120,"links":219},[220,221],{"id":168,"depth":120,"text":169},{"id":204,"depth":120,"text":205},"2026-10-01","We want to give Teeworlds communities a simple public page for their servers, live information and important links.",{"status":225,"project":130},"planned","\u002Froadmap\u002Flaunch-statustw-pages",{"title":137,"description":223},"2.roadmap\u002F2.launch-statustw-pages","vAE3vcCH8UdIfEHvhdFoGklyDPOSN0v6SC8DFeo6lv4",1785591733749]