This month I made a guide for how to self-host Tilemap Town because I realized that, although the amount of configuration required is very small, most people will want TLS and file uploads, so I wanted to explain how to do that. I would like to see what else I can do to improve the self-hosting experience but I'm unsure what kind of stuff people expect or need. It's mostly been minor fixes this month, with the main new feature being the morph UI.

Client changes:

• New UI for creating and managing morphs, accessed from "Character Settings".
• Added marker on the tab for when there are unread messages.
• The wall and floor options should now properly show up when editing a tileset definition.
• Added option to ignore clicks on the doodle board editing UI.
• /tailshift no longer tries to preserve a manually applied horizontal offset because it could get stuck when switching directions quickly. There's /tailshifto for the old behavior. There's also /tsh as a quick alias for /tailshift.
• You can now connect to servers without an encrypted connection on the login screen, to help with testing self-hosting setups.

Server changes:

• When you reupload a file that was used as a map wallpaper, the server now updates the map to use the new URL and notifies users.
• Fixed oversight where switching or creating morphs did not actually make a copy of your tags.
• New protocol command to get a list of your morphs.
• New icon for music files in the file browser.
• Block /pyexec and /pyeval by default, so that people self hosting do not unknowingly have a command that lets admins run arbitrary Python.

Site changes:

• Added Open Graph tags so tilemap.town links will have an icon.
• Fixed /userparticle examples to be correct for the new global tileset.