Meccha Chameleon Big Update 4.1.0 Patch Notes: New Maps, Server Overhaul, and Bug Fixes

Meccha Chameleon, the paint-to-hide multiplayer hit from solo Japanese developer and publisher lemorion_1224, released “BIG UPDATE 4.1.0” on August 28, 2026, and it’s easily one of the meatiest patches the game has shipped since its June 2026 launch. Two brand-new maps, a full replacement for the old server browser, and nearly twenty individual fixes and tweaks all landed in a single drop. What makes this patch stand out from the string of smaller hotfixes that came before it isn’t just the size of the changelog — it’s that the update touches three completely different parts of the game at once: content, infrastructure, and moment-to-moment feel. Below is a full breakdown of what actually changed, why each piece matters, and how it fits into the game’s development since launch.

A Quick Recap: Where the Game Stood Before 4.1.0

By the time Update 4.1.0 shipped, Meccha Chameleon had already spent nearly three months growing from a quiet two-person Steam release into one of the platform’s most talked-about multiplayer games. The run of patches leading up to 4.1.0 — Update 4.0.0, a Workshop-focused hotfix, fix4.0.1, and Update 4.0.2 — had mostly been about stability: fixing floating players, a teleport bug affecting Hunters, and cutting network usage. Update 4.1.0 is the first patch in that stretch to bring meaningful new content back into the mix alongside the ongoing infrastructure work, which is part of why it carries the “BIG UPDATE” label in its own announcement title rather than a plain version number.

What’s New in Update 4.1.0

Update 4.1.0 focuses on three pillars: fresh maps to paint yourself into, a rebuilt way of finding and joining matches, and a cleanup pass on bugs and performance issues that had piled up since the 4.0.x line began. Here’s the update at a glance before the section-by-section breakdown.

• Two brand-new official maps added to the public rotation: Kyoto and Art Museum
• Two existing maps, Greece and Egypt, reworked
• A complete replacement of the legacy server browser with a 5-character join code system
• In-progress games now hidden from public search by default
• Close to twenty individual bug fixes and quality-of-life adjustments
• A roughly 40% reduction in network data used while painting

New and Reworked Maps

The headline addition in 4.1.0 is a pair of new official stages: Kyoto and Art Museum. Both join the existing map rotation immediately and can be selected directly from the host’s map menu or included in random map voting. Alongside the new additions, two older maps received a visual and layout rework: Greece and Egypt were both updated as part of the same patch, though the official notes don’t go into specifics about exactly what changed on each — players jumping back into those two maps after the update should expect at least some layout or lighting differences from what they remember.

• Kyoto — new official map added to the public rotation
• Art Museum — new official map added to the public rotation
• Greece — reworked as part of Update 4.1.0
• Egypt — reworked as part of Update 4.1.0

Map	Status in 4.1.0	Notes
Kyoto	New official map	Follows earlier real-world-inspired maps like Osaka
Art Museum	New official map	Indoor setting, distinct from the game’s outdoor city maps
Greece	Reworked	Specific changes not detailed in the official patch notes
Egypt	Reworked	Specific changes not detailed in the official patch notes

Kyoto continues the game’s pattern of pulling inspiration from real Japanese locations, following earlier additions like Osaka, while Art Museum gives painters a very different kind of surface to work with — gallery walls, frames, and display cases instead of an open city street. Together they’re the biggest single-patch map addition in some time, and notably arrive shortly after an earlier August update had signaled that new official maps would slow down for a while, aside from collaboration content. Whether that plan changed in response to player demand or was always intended to resume after a short pause isn’t something the patch notes clarify.

Server Browser Overhaul

The other major piece of Update 4.1.0 is a full rework of how players find and join games. The legacy server browser has been replaced with a five-character alphanumeric join code system, which can also be verified directly in-game before you try to connect. This is a genuinely different way of getting into a match compared to how the game has worked since launch, and it changes a few habits players will need to adjust to.

• Legacy server browser replaced with 5-character alphanumeric join codes
• Join codes can be checked and verified from inside the game before connecting
• In-progress games are now hidden from public search by default (toggleable in options), so new players get funneled toward lobbies that are still waiting to start
• Server elapsed time is now shown directly on the search screen
• A round now ends automatically if the number of Hunters drops to zero while they’re still waiting to start
• Selecting a region tag is now mandatory before searching for a match

The move away from a browsable server list and toward short join codes is a significant workflow change, especially for streamers and content creators who regularly share a code on-screen for viewers to join. Instead of walking an audience through a list of server names and player counts, a host can now simply display a five-character code and let viewers type it in directly. It also pairs with the new “hide in-progress games” option, which addresses one of the more common complaints since launch: players joining a public lobby only to land in the middle of an active round with no way to participate until the next one starts. Making the region tag mandatory before searching is a smaller change, but it should help cut down on the kind of high-latency matches that happen when players accidentally search without a region filter applied.

Bug Fixes

Update 4.1.0 also clears out a solid batch of bugs, several of which had been reported repeatedly since earlier updates in the 4.0.x line. None of these are especially flashy on their own, but together they cover a wide range of small annoyances that had built up across matchmaking, controls, and stability.

• Fixed an issue where server player counts sometimes displayed as 0
• Fixed ammo settings resetting back to default every match
• Fixed a bug that could cause crashes for some players during gameplay
• Fixed stick-based paint controls moving at inconsistent speeds depending on framerate
• Fixed stick-based paint controls drifting slightly faster in the upward direction than other directions

The stick-based paint control fixes are particularly relevant for controller players, since inconsistent input speed when trying to fill in fine detail on a body model can be the difference between a convincing hide and an obvious outline. Pairing that with the earlier crash fix and the player-count display bug suggests the team spent this cycle working through a backlog of smaller reports rather than chasing one single high-priority issue.

Quality-of-Life Changes

Beyond the headline features, 4.1.0 makes a handful of smaller adjustments aimed at match pacing, performance, and general usability.

Category	Change
Taunts	Added a 1-second cooldown; increased the minimum forced-taunt interval from 1 second to 5 seconds
Networking	Reduced network data usage during painting by roughly 40%
Performance	Raised the maximum FPS cap from 239 to 240; reduced performance drops when opening the options menu
Voice Chat	Added a sound effect when toggling voice chat states on or off
Camera	Improved camera controls for Hiders during the hunt phase
Matchmaking	Region tag selection is now required before searching for a match

The 40% reduction in painting-related network traffic is worth calling out on its own, since the constant stream of color data from every Hider repainting at once has been one of the more strain-heavy parts of the game’s netcode. Combined with the new join-code system and hidden in-progress lobbies, the overall goal of 4.1.0 looks less like adding flashy new toys and more like tightening the plumbing under a game that grew far faster than a solo developer likely planned for. The taunt cooldown and forced-interval changes are smaller in scope, but they respond to a fairly common complaint in public lobbies about players spamming taunts to distract or annoy Hunters mid-round.

How the Update Fits Into the Bigger Picture

Looked at alongside the rest of the 4.0.x line, Update 4.1.0 reads like the payoff patch after several weeks of quieter maintenance work. Update 4.0.0 introduced the Petit Chameleon body option and fixed a handful of movement bugs. The Workshop hotfix that followed only touched mod map updating. fix4.0.1 targeted a specific teleport-related Hunter bug. Update 4.0.2 focused entirely on network usage and controller UI. None of those four patches added new maps or changed how matchmaking worked at a structural level — 4.1.0 is the first one in the sequence to do both at once, which is a large part of why it’s being treated as a headline release rather than a routine point update.

How to Get the Update

Like every previous patch, 4.1.0 downloads automatically through Steam the next time you launch the game — there’s no separate opt-in or beta branch involved. Because Meccha Chameleon requires matching client versions to play together, make sure both you and anyone you’re grouping up with have let the update finish downloading before trying to join the same lobby.

• No manual installation steps required
• Older clients cannot join lobbies running 4.1.0
• Workshop mod maps are unaffected by the server browser changes
• Existing join codes from before the update are no longer valid under the old server browser system

What to Watch For Next

Given how quickly lemorion_1224 has been shipping fixes since the 4.0.0 line started in mid-August, it’s a safe bet that a smaller hotfix or two will follow 4.1.0 to iron out whatever the new join-code system and the two new maps surface once millions of players get their hands on them. Past patches in this game’s history show a consistent pattern: a larger content or infrastructure patch is usually followed within a few days by one or two narrow fixes addressing whatever broke as a direct result. If that pattern holds, expect a smaller follow-up fix focused specifically on the new matchmaking flow before the next map-focused update arrives.