I love the idea of a transparent, public facing auditing API, and also see it as a potentially difficult thing to implement when we have a lot of work ahead of us already. I personally disagree that it is inevitable that this happens again, but maybe that is me being the naive one, time will tell.Celso wrote: Wed Jun 10, 2026 11:19 pm I guess each of these cases should be evaluated individually and not take a general rule, but in this one specifically I do think a permaban is warranted because of the treachery afterwards basis (he “naively” asks a not-so-bright GM, and when he sees he gets his way, he takes even more advantage, and then when caught, hes still more worried about what he’s going to gain / recover out of it).
I find it more important to publish the GMs questions, and some form of api or transparency mechanism so when this happens again (because is inevitable), you actually caught it in time.
This has been “easy” because is a relatively small realm, and progression is tracked between guilds / players. But if the realm grows to 2-3K simultaneous, good luck following the trail.
TL;DR:
Permaban, publish GM selection questionare, make each GM permission and/or actions auditable.
This was easy to catch not because it is a relatively small realm, but because our logging system is robust and audited. If this were to happen when our realm had 20k concurrent players we would be able to see the same results. If players had not reported this, our next audit (running the very next day) would have caught/flagged this and the results would have been the same, only potentially with a few more items to delete/punishments to dole out.