End of maintenance. Change logs.

Maintenance Successfully Completed
Check below the main fixes, improvements, and changes implemented.
Hello, Masters!
The maintenance has been successfully completed. Below you can find the main changes implemented.
1. Internal System Improvements
We have made several changes to our internal systems to improve game logging and monitoring.
These changes will provide our team with more accurate information for issue analysis, incident investigation, and player support.
2. Expander Fix
We fixed an issue that, in certain situations, prevented monsters from being properly stored in the Expander.
3. Upgrade (A) and (B) System Improvement
We have made an important change to the monster evolution system for (A) and (B) versions.
How did it work before?
When evolving a monster into its (A) or (B) version, the resulting monster was generated at its base level, causing the levels gained by the monster used as material to be lost.
How does it work now?
Starting with this update, the monster resulting from an (A) or (B) evolution will retain the level of the highest-level monster used as material.
Example
The result will retain the level of the highest-level Core used in the evolution.
Correction for Previously Completed Evolutions
Players whose monsters had their levels reduced due to the previous behavior of the system may request a level correction through Support, provided that all of the following requirements are met:
- The resulting monster must have been created within the last 45 days.
- There must be logs or records confirming that the monster's level was reduced due to the previous behavior of the Upgrade system.
- The player must provide the approximate date when the mix/evolution was performed.
4. Real-Time Game Updates
We have made changes to the server's internal structure to allow certain updates to be applied in real time, without requiring a server restart.
As a result, server restarts will only be necessary when they are actually required, reducing interruptions and periods of downtime.
5. Temporary Interface Update
We have temporarily updated some elements of the game interface, including the Card System, for testing purposes.
These changes are part of a transition phase while we continue developing the new MixMaster Online client, which is being built in 64-bit using a new engine.
6. Update to Skin Reward Rules for Reported Bugs
We are reviewing and implementing several changes to the rules regarding Skins granted as rewards for reported bugs.
A. Transferring a Skin Between Accounts
Players who own a Skin obtained through this reward system may request to transfer it to another account one time only.
Once transferred, that same Skin cannot be transferred to another account again.
B. Transferring a Skin Between Monsters on the Same Account
Players will be allowed to move a Skin to another monster belonging to the same account, including in the following situations:
- Selling or transferring the monster;
- Using the monster currently equipped with the Skin as material in a formula;
- Replacing the monster on which the Skin is currently applied.
Currently, this procedure requires submitting a Support Ticket. We plan to update and simplify this system in the new engine.
C. Changing the Skin's Appearance
Players may request to change the appearance of their Skin up to 2 times, provided that the following rules are met:
- The selected monster cannot be a BOSS-type monster (King Garugon, Anubis, etc.) and the requested version must not already exist in the game.
- The selected Skin cannot have an excessively small sprite.
- All requests are subject to review and approval by the responsible team through a Support Ticket.
Criteria for Receiving a Skin
These rewards are granted primarily based on the severity, impact, and relevance of the reported issue, following a review by the responsible team.
Therefore, reporting multiple issues or repeatedly requesting a reward does not guarantee that you will receive a Skin. The decision is made exclusively by the team responsible for reviewing reported bugs.
Issues that are exclusively visual, highly specific, or limited to a particular character, and that do not have a significant impact on gameplay, security, the game economy, or game balance, are generally not considered high-severity issues.
Our goal with this system is to recognize players who contribute to identifying relevant issues with a significant impact, helping our team maintain a more stable, secure, and balanced game environment.
Thank you all for your cooperation and understanding during the maintenance.
Best regards,
MixMaster Online Support Team

