#Minecraft server status Offline

#Minecraft server status Offline

Make sure you are using the correct endpoint when retrieving a server status, as attempting to use the Java Edition status route with a Bedrock Edition host (or vise-versa) will result in a response saying the server is offline unless the server explicitly has cross-play supported. Supported VersionsĪll Minecraft servers, including pre-netty rewrite Java Edition and Bedrock Edition servers, are supported. If you want to bypass the cache, we recommend that you self-host the ping-server available on our GitHub organization. No exceptions will be made to the cache duration. Wait for it to finish generating a new world. Delete the existing world folder: Start the Minecraft server. Next you will need to create a fresh world, then replace that with your original world. Any request made after this cache expiration time will result in fresh data being retrieved on our end. Delete the seed number so that the line reads: Save and exit the file. The response will also contain a X-Cache-Time-Remaining if the cache was hit, which contains an integer with the amount of seconds remaining until the cache expires for this request. All routes with data retrieved from the cache will contain a header in the response with the key X-Cache-Hit which will contain a boolean value whether or not our service used a value from cache. Please note that adding query parameters to the request will not force a fresh request, it will still return the cached response. Each route has its own cache duration, unique to the pathname of the request. To reduce the amount of spam and deliberate denial-of-service attacks of our service, we implement a caching system for all of the data we fetch, including but not limited to status responses and server icons. You may learn more about the properties you receive from these routes by reading the documented response body from the route on this page. All JSON returned from this service will have whitespace and any unnecessary characters removed to reduce network bandwidth and wasted information. No other data formatting standard is available at this time, and there is currently no future plan to support anything other than JSON. All status endpoints return a response body in JSON format. You will never have to use POST or any other method with requires you to send body data or headers with your request. We currently only support endpoints using the GET method. The majority of this API uses the standardized REST API, which in simple terms means you will be making HTTP requests to our service. If you believe there is anything missing, any typos, or incorrect information on this page, please reach out to me via email at. This page will go over everything you need to know before implementing our API into your service. The goal of this API documentation is to accurately and precisely describe the functionality of this service in plain terms.