-
Notifications
You must be signed in to change notification settings - Fork 263
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
[Bug]: Lib:Token can no longer be found #4654
Comments
I've been having the same error ever since switching to 1.14 from 1.13. The error doesn't always trigger, it was like 50% chance of triggering so i would just open up the campaign file again. But lately it's been more like 95%. Even if i delete my lib token and save it that way, the error continues this time not even showing error and opening a blank maptool file instead of the campaign file. Another thing i found is that the "95% chance of erroring" is retroactive meaning that i save my campaign files regularly while working on my framework and the older versions of my campaign files have the same chance of error. So it isn't a very broken macro triggering, i use oncampaignload for defining functions and i tried to delete all my defined functions and save it that way. Didn't solve the problem. |
I think you're going to have to share the problem campaign file. If this was a common issue we'd be seeing a lot more reports. |
I believe this is the same underlying issues as #4542. |
Describe the Bug
When starting MapTool 1.14.3, the first time I try to load a campaign file, maptool takes quite a while to do so (15 seconds for a campaign with no contents: campaign file is 15 kB).
"net.rptools.maptool.model.library.LibraryNotValidException: Lib:Token can no longer be found."
Subsequent attempts to load campaign files in the same instance of MapTool work perfectly: campaign files load quickly and correctly, whether they have a library token or not,
To Reproduce
Expected Behaviour
The campaign file should load.
Screenshots
No response
MapTool Info
1.14.3
Desktop
Windows 11 Pro
Additional Context
maptool.log
The text was updated successfully, but these errors were encountered: