Windows 7 or newer (Can be tested on uggly old XP) So do not ask about sources and updates, that is rude.

This files will receive future & free updates. At client side i developed from scratch, like my season 4.5 server files. I have rewrote a lot of code in server-side, it is based on X-Emu sources, but is not like a MUEMU copy or repack, it is a new server and more incoming. The purpose of this server is provide a good and stable server with customs that do not make an alien version of MU Online. Was processing at the time of the log entry.Hi all, i am here to release a new server files based on Season 5.5 GMO protocol.Īnd after developing this server since (July 3) it reaches a stable state, that mean it can be tested without terrible bugs.

Finally, you’ll see some sort of textual output, often a helpful messageĮxplaining why the log was written, or perhaps a copy of some data which Mu.

See the Python documentation on logging for what they mean. Of the following values: DEBUG, INFO, WARNING, ERROR or CRITICAL.

Next comes an indication of the type of log entry this is.

Following this, in parenthesis, is the name of the function being evaluated.

Next comes the name of the file and the line number that generated the log.

It starts with the date and time of the log entry, YYYY-MM-DD HH:MM:SS.

Makes it easy to visually find restarts in the log file.Įach line in the log file follows a pattern:

16:51:22,519 - mu.logic:560(restore_session) INFO: Restoring session from: /home/ntoll/.local/share/mu/session.jsonĮach time Mu restarts it emits a line of dashes:. 16:51:22,518 - mu.logic:856(change_mode) INFO: Workspace directory: /home/ntoll/mu_code 16:51:22,467 - mu.logic:521(setup) INFO: Available modes: python, adafruit, microbit, debugger, pygamezero

Mu server files