Ender

Calling it the Viridia table is probably a misnomer. It's just the first table in the cmode section of the itemPT, which happens to be the same slot used by 'Viridia' for the normal mode tables. This CM table is the one and only table for CM. The other tables are mostly copies of the normal mode tables, so using those would give you stuff like ABeast weapons dropping in Forest or Native in Ruins, for example. The CM table is not identical to any table used for normal mode. The shot chance in this CM table is 6%, whereas Viridia in normal mode is 11%. For reference, thi

You still DC on Ephinea after some number of detected desync issues, or earlier if the desync leads to something horribly wrong from the server's perspective. Section IDs shouldn't matter for CM. There's only one table defined for CM in the itempt and it's just the first ID table, which happens to be Viridia. From Soly's post, sounds like Ultima is using that table correctly.

There's nothing in the log because the fonts are changed outside of the lua context, so it can't really throw a stack trace into the log, but there's probably a way to add something into the log regardless. The addon tells the plugin to load a font with some settings, the plugin does it between the next frames for the addons. There definitely are some cases to fix in the error handling and I'll try to fix that this week, as well as add something to tell you that it failed to load a font and at least an error code. With those fixes, at least it'll revert to the old default bitmap font that

Weird. I haven't seen this with the Settings Editor changes. Did you also install the addons/fonts folder included from soly's updated plugin dll? Assuming you did install the fonts folder correctly, one thing you can try is going into addons/Settings Editor folder and renaming the options.lua. Then try reloading addons or relaunching pso. It should generate default options which load the old font. EDIT: Someone else just posted the same issue on discord for another server. For them, they were able to workaround it by removing the Settings Editor addon. I'll look into why it's break