Transformice is a multiplayer online platformer where players (mice) cooperate to retrieve cheese and return it to their hole. The term “Transformice API” typically refers to ways developers and community members interact programmatically with the game or its ecosystem: official and unofficial endpoints, bots for rooms, chat/administration automation, and community-made libraries that parse game data. This article summarizes what the Transformice API landscape looks like, common use cases, implementation notes, and best practices.
When Transformice switched from Flash to HTML5 (Unity WebGL), many internal API structures changed. Old guides (pre-2020) referencing FlashVar or ExternalInterface are obsolete. The current Lua API is sturdier but slower.
Melanie (Atelier 801’s lead developer) has historically been private about API roadmaps. However, recent trends in the community suggest three developments: transformice api
The external API throttles aggressively. If you try to fetch stats for 1,000 players in one minute, Atelier 801’s firewall will block your IP. Always cache results (e.g., store stats in Redis for 10 minutes).
For data analysis or Python-based bots, there are several wrappers available on PyPI. The external API throttles aggressively
Transformice modules (if enabled on your server) support the tfm.exec.httpRequest function. This allows your game mod to POST data to your web server.
Use Case: Recording every death in a competitive room to a MySQL database. map = tfm.get.room.currentMap
Lua Code:
function eventPlayerDied(name)
local data = json.encode(player = name, map = tfm.get.room.currentMap, time = os.time())
tfm.exec.httpRequest("https://your-api.com/log_death", "POST", data, "application/json")
end
Server Code (PHP/Node): Your server receives the JSON, validates the IP (check if it matches Atelier 801’s ASN), and stores the data. This creates a real-time analytics dashboard for your community.