How to prevent and handle improper account sharing on your MU Online server

Account sharing in MU Online is a gray area most servers would rather not regulate until the problem shows up: a player complains that they "lent" their account and the friend changed the password, two clans dispute ownership of an endgame character bought informally, or a group rotates logins to keep a character farming 24 hours a day without directly breaking the bot rules. This tutorial explains how to set a clear account sharing policy, which technical signals point to misuse, and how to respond to disputes without the server becoming an arbiter of agreements it never should have mediated.

Why account sharing is a server problem, not just a player-to-player one

When two players share an account informally, the risk seems to belong only to them — but it becomes the server's problem the moment one of them opens a support ticket asking for a password reset, item reversal, or a ban on the "intruder." Without a clear policy, the support team is forced to investigate ownership disputes it has no way to prove, wasting time and creating the perception that the server "picks sides." Defining the policy before the first case appears avoids improvised, inconsistent decisions.

Differentiating types of sharing

Not all account sharing carries the same risk. Classify cases before deciding on policy:

Defining this classification in the server's public policy (rules/terms of service) gives you an objective basis to act when a case comes up.

What to put in your terms of service

Be explicit, avoiding ambiguity that becomes ammunition for disputes later:

5.1 - Informal account sharing between people trusted by the
      account holder is tolerated, but the original account holder
      (identified by the registration email) is the only party
      recognized and supported by staff.
5.2 - Selling, renting, or transferring an account for payment is
      prohibited. Accounts identified in such transactions may
      be suspended.
5.3 - The server does not arbitrate ownership disputes between
      third parties who informally shared an account. Password
      recovery and support always follow the original registration
      email.

That last point is the most important one operationally: it gives support an objective rule ("follow the registration email") instead of asking the agent to decide who's right.

Technical signals of rotation and sales

Set up logs and alerts for the following patterns, without needing to access the player's personal content:

Limiting concurrent sessions on the server

Most emulators let you limit concurrent logins per account. Enable this lock to prevent, at minimum, two active sessions at the same time with the same login:

[AccountSystem]
AllowMultipleLogin = 0
MaxConcurrentSessions = 1
KickOldSessionOnNewLogin = 1

This doesn't prevent sequential rotation, but it eliminates the most common dispute case: two people logged in at the same time, each thinking they have exclusive simultaneous control of the character.

Logging IP and time history per account

Keep a simple log table linking account, IP, and timestamp for each login. This isn't for spying on the player, but to have a comparison baseline when a dispute or suspected sale comes up:

SELECT account_id, ip_address, login_time
FROM account_login_log
WHERE account_id = 'ACCOUNT123'
ORDER BY login_time DESC
LIMIT 50;

An abrupt jump in IP region, combined with a change in play pattern, is the most reliable signal of an undeclared ownership change — more reliable than just the number of distinct IPs, which can be explained by mobile internet or a legitimate VPN.

Ownership dispute response protocol

When two players open tickets disputing the same account:

1. Don't take sides immediately. Explain that support follows the registration (original email) as a matter of policy.
2. Request objective proof only from the registered holder (access to the registration email, answering security questions if any exist).
3. Don't reverse items or characters moved during the shared-access period — the server has no way to arbitrate what was transferred in good faith versus what was a scam.
4. Enforce the sale/rental ban policy if there's clear evidence (a chat screenshot confirming payment, for example), suspending the account per the terms.
5. Document the decision internally for consistency in future cases.

Cases where preemptive suspension is warranted

Suspend the account (not necessarily ban it) while investigating when: two people simultaneously claim to be the holder, there's evidence of a recent sale, or the usage pattern suggests combined use with an unauthorized boosting service. A temporary suspension protects the account from further movement while support decides, without prematurely punishing whoever might be the legitimate holder.

The difference between account sharing and rotational botting

It's important not to conflate the two when communicating with the community: account sharing by itself is not botting. The problem arises when manual rotation replaces the need for bot detection — a group keeping a character active 24h through human rotation has the same economic effect as a bot, but technically doesn't violate the "no automation software" rule. If this is undesirable on your server, explicitly state in the rules that coordinated rotation for continuous farming is also prohibited, regardless of whether software is used.

Common errors and fixes

Account sharing policy checklist

• Terms of service with a clear clause on sharing, sales, and ownership disputes.
• Concurrent session limit configured in the emulator.
• IP and login time history log active per account.
• Ownership dispute response protocol documented and followed by the team.
• Explicit rule against coordinated rotation for continuous farming.
• Preemptive suspension defined as standard practice for active disputes.

With the account policy defined, it's also worth reviewing the security controls of the infrastructure that hosts this player data — the MU Online server setup guide covers the foundation this account system is built on.

Frequently asked questions