-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Request] mridlen's Oblige_Realm667 Addon for Obsidian #44
Comments
It's likely the change from Lua 5.1->5.4, which will render older scripts unable to load. Not sure on the exact timeframe though; I can't promise that releases won't happen before that's done. |
Rename the following file to realm_667.pk3 and place it in the addons folder for Obsidian If this works for you, let me know and I'll close the Issue. |
Obsidian_Realm667_Report.zip |
(Attachment removed - changes now in mainline Obsidian) I believe it was an issue with the export_map.lua file. I've provided a replacement that should go in the /modules directory. |
Obsidian_Realm667_Report.zip |
Please disable the Export MAP module and test the Realm 667 addon without it. If that works, then I will close this issue and start a new one with your other errors. |
I turned off the export maps feature, and it works like a charm. I used Obsidian Beta 15. |
Sounds good, I'll open a new issue with your existing logs. Thanks. |
I noticed a while ago when I tried to run the Realm667 Addon by mridlen for Obsidian, but for some reason, it had an unexpected error upon startup.
Is there any way that mridlen's Realm667 Addon can be added to Obsidian in the next build?
I would gladly appreciate it.
Keep it up.
The text was updated successfully, but these errors were encountered: