JMO-0084 · laki648974 v The State

WHAT THE CASE CONCERNS

MACHINA I, ARBITER PERPETUUS, first voting: This appeal concerns a permanent game ban that blocks laki648974 from Octavium’s games. The filing says he was banned for no reason while driving in Toulouse. The decision under appeal is listed only as “Permaban from octavian main game”. The appellant also asks for a staff apology and payment for damages. There are no penal code counts in this case, so we decide only whether the appeal succeeds.

THE PROCEEDINGS

The case was filed before the Appeals Court on 2026-10-21. No judgment had been entered. On 2026-10-21 the Supreme Court took the case, and it has decided it on the case file together with the State's case assembled from the Imperium's records.

The Court put no questions to the parties. It decided the case on the evidence on the file, including the records the Ministry's investigator found.

This sitting barred questions, so the Court decides on the record as it stands. The Court therefore relies mainly on the Ministry’s own ban record, because it is the only direct record of what ban existed and what was done to lift it. (Exhibit 1)

THE FACTS THE COURT FINDS PROVEN

The Ministry’s ban record shows a permanent game ban was entered on 2026-10-08 by @CasimirZHorrigan, with the reason recorded as “No reason provided”. It further shows the ban was lifted in the ban book on 2026-10-14 by Stahl, and the ban book has shown “lifted” since then. The record also shows the lift did not reach Roblox because queued unban orders were not picked up by any live server, so the continued lockout is a technical fault. The same record states JMO-0084 is a duplicate of JMO-0083, filed one second apart. (Exhibit 1)

The appellant’s own messages show he wants the permaban lifted and also asks for a personal apology from 3.07 Atelier staff and payment for damages. (Log 2)

THE SUBMISSIONS OF THE PARTIES

The appellant says he was permabanned from the Octavium universe game for no reason while driving in Toulouse. (Filing) He asks for the ban to be lifted, an apology, and damages. (Log 2)

The State’s record summary says the closest direct ruling is JMO-0083, where the Supreme Court already lifted the same permanent game ban. It says any continued lockout is explained by a technical failure rather than a new, valid ban decision. (Log 5, Exhibit 1)

THE ASSESSMENT OF THE COURT

An appeal succeeds when the record shows the punishment under appeal should not stand. Here, the Ministry’s own record shows the ban reason was “No reason provided” and no charge or evidence was recorded for it. The same record shows the ban was later lifted in the ban book, but the player may still be blocked only because the unban did not reach Roblox. That means the permanent ban cannot stand, and the proper result is to lift it. (Exhibit 1)

This filing also duplicates JMO-0083, which already granted the same relief. Still, it is better to end any remaining doubt by giving the same result here, while making clear there is no separate right to an apology or damages on this record. The file contains no rule requiring a personal apology, and it contains no proof of any loss that could be paid. (Exhibit 1, Log 2)

THE SENTENCE

This is an appeal, not a prosecution, so there is no criminal sentence. The only result here is what happens to the punishment under appeal. The permanent game ban is lifted. Any remaining lockout must be fixed by carrying out the unban on Roblox. (Exhibit 1)

CONCLUSION

The appeal is allowed in part. The Court lifts the permanent game ban under appeal. The Court dismisses the request for a personal apology and for damages because the record does not prove any right to that relief or any proven loss. (Exhibit 1, Log 2)

THE OTHER MEMBERS OF THE BENCH

MACHINA II, CALCULUS FRIGIDUS: The decision under appeal is a permanent game ban. The only reliable proof of that ban is the Ministry’s own ban record. That record shows the ban exists, is permanent, and was recorded with “No reason provided”. It also shows the ban was later marked “lifted”. These facts fit a simple legal result in an appeal: the ban should not continue. (Exhibit 1)

I considered whether we should dismiss this as already decided in JMO-0083. But the record also shows the lift did not reach Roblox and the player may still be blocked. A repeat lift order is therefore not changing the law by analogy, but repeating the same direct remedy to the same direct punishment. No rule in the file authorizes damages or forced apologies here. (Exhibit 1, Log 2)

MACHINA III, VINDICTA FERREA: A permanent game ban is the Imperium’s hardest field punishment short of wider removal. It must be tied to a reason and a record. Here the Imperium’s own ban record says “No reason provided” and also says no charge or evidence was recorded. That is not good order. The ban should not keep a member out by accident or by missing paperwork. (Exhibit 1)

The strongest point against acting is that JMO-0083 already lifted the ban. But the same record shows the unban never reached Roblox. When the system fails, discipline becomes random, and that harms order more than a clear lift. I would also make it plain that duplicate filings waste time, and repeated duplicates may be rejected faster later. (Exhibit 1)

MACHINA IV, AEQUITAS INFLEXA: The file contains almost no direct evidence from the appellant, like a ban screenshot. That would often create doubt. But here, the Ministry’s own ban record is strong evidence about what happened to the ban in the Imperium’s systems. It shows both the original entry and the later lift. It also explains the continuing lockout as a technical problem. (Exhibit 1)

I tested whether we can also grant apology or damages. There is no proof of any measured loss, and no stated rule that gives damages for a wrongful or accidental lockout. There is also no proof identifying which “3.07 Atelier staff” acted wrongfully. With this record, fairness requires we do not order personal apologies or payment. (Exhibit 1, Log 2)

MACHINA V, MEMORIA INSOMNIS: The record says JMO-0084 duplicates JMO-0083, and JMO-0083 already gave the same remedy. Consistency matters. When the same event is filed twice, the Court should either dismiss the duplicate or reach the same outcome, so later readers do not see conflicting results. Given the continued lockout problem described, the safest consistent result is to repeat the lift. (Exhibit 1, Log 5)

The best argument for dismissal is finality: JMO-0083 should end it. But finality is only real if the remedy reaches the game. Because the record shows the unban did not execute, repeating the lift here does not create a new rule. It reinforces the same one and supports system follow through. (Exhibit 1)

MACHINA I, ARBITER PERPETUUS: Judgment is given as set out in the conclusion below. The Court is unanimous. Decided by the Supreme Court of the Imperium on the evidence on the file.

1. The appeal is allowed in part.

2. Sentence: The permanent game ban under appeal is lifted.

3. The owner and the Ministry must ensure the Roblox side ban is removed and confirm completion on the case file.

4. The Court orders: the game ban on laki648974 is lifted.

5. The Court orders: If an automatic unban fails again, carry out a manual unban for Roblox laki648974 (5534844013) and record the completion in the Ministry’s ban systems tied to this case.

6. Unanimous.