Veterans of online gaming rarely hold a soft spot for macros. Back in the day, macros typically referred to programs in MMORPGs like Lineage that autonomously hunted monsters and gathered items without human input—the classic "auto-play." Critics argued these programs ruined fairness and sucked the joy out of the experience for honest players, leading to a strong consensus that macro usage deserved a strict ban.

Yet, times have changed, and so have macros. While shady auto-play bots that outright replace human control still exist, modern gaming keyboards and mice often feature built-in functions to assist with repetitive key inputs. The catch? Some publishers fail to make distinctions, slapping a permanent ban under the all-encompassing umbrella of "using unauthorized programs."

Sure, banning macros that rely on unauthorized software is entirely understandable. But in an era where macro-enabled hardware is everywhere, is hitting every single use case with a permanent ban really justified? In this installment of precedent.zip, we revisit past account-suspension cases involving Lineage macros to ponder whether those vintage rulings still hold water in today's gaming landscape.

Let us wind the clock back to 2007. Two Lineage players found themselves staring at permanent account suspensions for allegedly using unauthorized auto-play programs. Both had been enjoying the game since 2002, and NC confirmed their use of auto-play software, dropping the hammer with permanent bans in May 2007.

Naturally, the players fought back by filing a lawsuit, demanding the lifting of their bans along with one million won each in damages for emotional distress. Interestingly, neither player contested the fact that they actually used unauthorized auto-play programs. Instead, they argued that a permanent ban for a single infraction was disproportionately harsh, and that the terms of service lacked clear definitions regarding prohibited programs and the resulting penalties.

On the flip side, the publisher countered that powerful penalties were vital since auto-play programs dismantle the natural order of the game. They specifically highlighted the fact that both users had rented out their accounts to so-called "leveling offices"—enterprises that took cash to grind characters on behalf of others.

In this round, the court ruled in favor of the publisher. The reasoning was that auto-play programs operate twenty-four hours a day without human supervision, thereby destroying the core system of the game, dampening the enthusiasm of other users, and putting unnecessary strain on game servers. Factor in the account rentals to leveling offices, and the permanent bans could hardly be deemed overly harsh.

While the plaintiffs' claims were dismissed, the real takeaway lies in why the court deemed the permanent bans justified. The court broke down the unauthorized programs used in the game back then into three distinct categories: ▲ speed hacks that accelerated character action speeds; ▲ ghost mice that automated health recovery without extra inputs; and ▲ auto-play programs that handled everything from monster selection to combat and potion consumption.

The court did not treat these programs as equals. Crucially, it viewed auto-play programs as a far more grave violation than speed hacks or ghost mice because they fundamentally shattered the core structure of gameplay, which relies on a user's instantaneous judgment and control.

The publisher's operational policies at the time reflected these nuances. According to the ruling, the policy applied to the second user permitted a permanent ban for a first-time offense involving malicious auto-play programs, while stepping down penalties for supportive auto-scripts—such as heals and buffs—to a first-time warning, a ten-day suspension for a second offense, and a permanent ban only on the third. Clearly, not all macros were lumped into the exact same severity tier.

The court similarly weighed the impact each program had on the game and how severe the violation was compared to others before validating the permanent ban. Though it is an eighteen-year-old ruling, it remains well worth pondering when tackling today's macro dilemmas.

An even more famous ruling regarding macros emerged from the Supreme Court in 2010, stemming from yet another Lineage auto-play dispute. At the time, NC's operational policy mandated a permanent ban for even a single use of an auto-play program. Furthermore, if three or more accounts owned by a single user were permanently banned, the publisher reserved the right to restrict access to all remaining accounts. The user naturally argued that such sweeping penalties were overly harsh and unfair.

Once again, the Supreme Court sided with the publisher. It reasoned that because an auto-play program can run continuously once installed, penalizing just one account would leave the culprit free to fire up another and keep right on botting. The risk of mass item hoarding through auto-play for cash-trading purposes also served as a crucial pillar for the ruling.

In addition, the court factored in that the publisher had individually notified users of the terms and operational policies, and that hitting three accounts was a prerequisite for restricting the rest. Ultimately, the Supreme Court concluded that these clauses were neither unfair nor in violation of the principle of proportionality.

This verdict became a cornerstone precedent backing up robust publisher sanctions against macros. Still, we need to pause and clarify one vital point here: the Supreme Court did not endorse a blanket rule stating that "all kinds of macros deserve permanent bans." Rather, the judgment factored in the specific havoc wreaked by auto-play programs at the time, violations across multiple accounts, and proper notice and consent procedures regarding operational policies. So, can we blindly apply that exact logic to every modern macro function today?

Let us fast forward to the present day. Modern gaming keyboards and mice often come packed with features that let you execute multiple commands with a single keystroke or automate repetitive inputs. Imagine a user keeping their eyes glued to the screen while playing, but bundling repetitive key presses into a single tap. Contrast that with someone who configures a program to roam and hunt monsters independently while stepping away from the keyboard. Both share the common trait of automated input, but claiming they have the exact same impact on the game is a stretch.

Of course, utilizing built-in keyboard features is not a free pass. Depending on the game, simple repetitive inputs might grant unfair advantages over other players or compromise fair play. While publishers have every right to ban such actions in their terms, the real nuance lies in evaluating what the function actually automated and what impact it truly had on the game.

We also need to dissect the phrase "unauthorized program" thrown around by publishers. Just because a publisher disapproves of a program does not mean it constitutes an illegal act under civil or criminal law, as rule violations inside a game are entirely distinct from breaches of statutory law. Above all, deciding that a term of service was breached is one thing; deciding whether slapping a permanent ban for that breach is justified is an entirely different beast. Shouldn't we be looking at the nature and severity of the violation, repetition, actual gains acquired, and the fallout for other players all at once?

There is another layer to consider: the economic value of gaming accounts. These days, sinking years into leveling characters, opening the wallet for hefty microtransactions, and securing rare gear is par for the course. Depending on the game, characters and items can change hands for thousands of dollars. What happens when an account like that gets permanently banned over a single macro instance? Everything the user invested—time, money, and in-game achievements—vanishes in a puff of smoke.

The core hurdle is that under current legal frameworks, gamers struggle to claim standard ownership rights over digital items. Because virtual items reside on servers managed by publishers, the baseline legal structure treats users as mere licensees bound by user agreements.

That does not mean virtual items lack economic value. A Supreme Court ruling from April 13, 2012 (2011Du30281) regarding the repeated buying and selling of Lineage game currency determined that virtual currency counts as "goods" under the Value-Added Tax Act. While acknowledging virtual goods for tax purposes does not automatically translate to granting civil ownership rights to users, it creates a rather odd paradox: the system recognizes enough economic value to tax real-world trades of game currency, yet defaults to standard terms of service when dealing with the catastrophic loss of accounts through permanent bans.

Nobody disputes the necessity of publisher operational rights. Even so, given the heavy economic weight attached to modern gaming accounts, shouldn't we pay closer attention to the immense value users forfeit when hit with a permanent ban?

Lately, we have seen instances where users actually win lawsuits against publishers over account suspensions. However, those victories typically revolved around proxy play or other distinct disputes rather than macro usage. Because macros directly undermine fair play and infringe upon the rights of fellow users, courts have traditionally taken a hardline stance, making user victories against publishers hard to come by.

The 2008 and 2000-era rulings we looked at earlier also validated harsh publisher penalties. Yet the courts upheld those permanent bans not simply because "a macro was used," but because of concrete aggravating factors: twenty-four hour automated farming, hoarding massive amounts of items for cash trading, and inflicting direct harm on legitimate players. Notably, the 2008 ruling went out of its way to differentiate the severity of auto-play programs from other auxiliary tools.

Can we honestly apply that exact same yardstick to simple repetitive inputs driven by keyboard or mouse macro features? While old precedents do not provide a blanket answer, we must recognize that past macro rulings did not universally justify permanent bans across every conceivable form of automation.

Furthermore, we must separate the right to ban macros from the right to permanently ban accounts. Publishers absolutely need to ban macros to protect honest players and maintain a level playing field. But possessing the right to forbid macros does not automatically mean every single macro infraction warrants a permanent ban. Should a program that completely replaces human presence for round-the-clock farming be treated with the exact same severity as a quality-of-life macro that merely handles repetitive keystrokes while the user sits right there playing?

Furthermore, a modern gaming account is far more than a mere login credential. It represents years of character progression, hard-earned gear, and a cumulative investment of time and money. Permanently banning such an account carries a completely different weight than a temporary suspension. While user violations of terms cannot be hand-waved away just because an account holds economic value, publishers can no longer assume that wielding a permanent ban is always justified the moment a rule break is detected.

What matters most is achieving a fair balance between the substance of a violation and the resulting penalty. The auto-play programs judged by courts eighteen years ago look vastly different from today's diverse macro utilities. When weighing modern disputes, we need to push past the lazy question of "Did they use a macro?" Instead, we must closely inspect the specific features used, their actual impact on the game, and whether a permanent ban represents a proportional response. That is precisely where courts will need to focus their scrutiny in future macro battles.