Jump to content


  • Posts

  • Joined

  • Last visited


4 Neutral

About Ender

  • Rank
    Rag Rappy
    Rag Rappy

Profile Information

  • Gender

Recent Profile Visitors

1,554 profile views
  1. There's a choice for server in the Item Reader's configuration window. Select Ultima and that should fix it.
  2. The 'dark chao' mag on the left is a reskinned regular Chao mag. The mag on the right is a reskinned Naga except two of them, similar to Twin Sato. I know they have some sonic theme for an event and a 'new enemy' using a Robotnik model, but I was under the impression those were model replacements and not new models added into the game. Could be wrong.
  3. 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, this CM table is 13% Sabers/Handguns/Canes, 7% Swords/Daggers/Partisans/Rifles/Mechguns/Rods/Wands, and 6% Slicers/Shots.
  4. 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.
  5. 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's embedded in the plugin. I'll probably also add a way to disable the settings editor from the configuration menu as well.
  6. 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 breaking. EDIT2: Are you running this in Windows or in a VM/WINE? Just trying to narrow down what's causing this issue.
  • Create New...