Admin Operations & Events

The Prime Directive: Zero Human Bias

A core tenet of SourceRO is removing the “Admin” from the game world as much as practically possible. Historically, Ragnarok private servers fail because of a breakdown in trust: Game Masters (GMs) playing favorites, secretly spawning items, or selectively enforcing rules.

To eliminate corruption, SourceRO treats the Admin not as a god, but as a mechanic. GMs exist strictly to maintain the infrastructure, not to interfere with the simulation. All in-game activities are bound by absolute, publicly verifiable protocols.

1. Automated, GM-Less Events

If a GM manually spawns an MVP event or hands out prizes to players in Prontera, it opens the door for favoritism and subjective rewards. Therefore, all server events are entirely scripted.

• No Manual Spawns: GMs cannot manually summon monsters, drop items, or trigger server-wide buffs on a whim.
• Script-Driven Activities: Classic events (like Poring Catcher, Disguise Event, or weekend modifiers) are hardcoded to trigger on specific schedules, server uptime metrics, or mathematically verified community milestones.
• Open Source Logic: The scripts dictating event rewards, spawn rates, and schedules are publicly available in our GitHub repository. You can verify exactly what the prize tables are and confirm that the odds are fair.

2. Moderation & Transparent Justice

Rule enforcement must be clinical, swift, and entirely transparent. We do not conduct closed-door investigations or hand out secret bans.

• Public Ban Logs: Every single account suspension is automatically broadcasted to a read-only #ban-logs Discord channel, complete with the reason and the specific rule violated.
• Evidence-Based Action: Bans for botting, macroing, or RMT (Real Money Trading) are executed based on verifiable data (packet logs, trade logs, or definitive video evidence).
• No Secret Pardons: Once a ban is executed, it can only be overturned if undeniable counter-evidence is provided. There is no “VIP treatment” for big spenders, streamers, or high-profile guild leaders.

3. Economy Intervention & Item Restoration

The server economy is a closed loop. The moment an Admin generates an item out of thin air, the integrity of the Glass Server shatters.

• Zero Item Generation: GMs are technically restricted at the database level from using @item, @produce, or @zeny commands on the live server.
• The “Tough Love” Restoration Policy: We do not restore lost, scammed, or accidentally dropped items. If an account is compromised due to poor password security, or if a player accidentally sells an MVP card to an NPC, the item is gone. Allowing restorations requires Admins to possess the power to print items, which fundamentally violates our core architecture.

4. Player Support & Issue Tracking

In-game support is decentralized and automated wherever possible to reduce GM dependency and eliminate wait times.

• Automated Utilities: Players have access to robust player-commands like @unstuck to resolve basic geographic glitches or client desyncs without needing to wait for a GM to log in.
• Public Issue Tracking: Server bugs, exploit reports, and mechanical issues are handled via GitHub Issues or public Discord threads. When an exploit is patched or a bug is fixed, the code commit is linked directly to the public issue for complete transparency.