After our recent
infrastructure migration has brought several server-side bugs that are affecting many users. You can track known issues here.
Resolutions to these issues will be introduced periodically by Skeight, our site administrator.
┌──────────────────────────────┐
Workarounds Available/Work in Progress
└──────────────────────────────┘
Internal Server Error
The internal server error occurs when our servers attempt to display a map that is stuck in a specific errored state. The exact cause has yet to be identified.
A temporary solution has been implemented that forces errored maps to appear. These entries cannot be deleted and will not show up for other users.
An example entry can be seen below.
[img] [Image: zTsaMEp.png]
Screenshot Editor Missing
Several users have reported that the screenshot editor may not load after a successful upload.
This is an account specific issue that occurs in particular browsers. Use another browser to get around this issue.
An example of the problem can be seen below.
┌──────────────────────────┐
Unresolved Issues
└──────────────────────────┘
Maps Are Not Rendering 1.12 Blocks
Due to the dissapearing of our site administrator, our render service does not yet offer proper rendering support for 1.12. Your 1.12 map should still render correctly.
1.13 Maps Are Not Rendering
Our service does not support pre-release version of Minecraft.
Due to a major change in Minecraft's region format, our rendering service will fail to render all 1.13 maps.
Render Not Updating
Due to a server-side issue with reading newly uploaded level.dat files, some renders will fail to update with the following error.
[img] [Image: PHulZVk.png]
┌──────────────────────────┐
Resolved Issues
└──────────────────────────┘
Uploading Screenshots Results in Error 500
A new HTML5 uploader has been implemented!