If you right click while the program is loading into a campaign you get the following error (this is two right clicks)
https://puu.sh/rZ1HD/56bac6a2b1.png
Printable View
If you right click while the program is loading into a campaign you get the following error (this is two right clicks)
https://puu.sh/rZ1HD/56bac6a2b1.png
Don't remember seeing this one mentioned. It appears in any of the Core based rulesets I have. As soon as you start typing in the "Name" field it appears. You can actually type a whole word one console error at at time but you get a "Module export failed" error.
Updates
- Number negation via CTRL key disabled when dragging from hot key.
- [CoreRPG+] Negative parcel coin amounts allowed once again.
- [CoreRPG+] Missing title and script error when editing name field in export window. Fixed.
- [SW] Deadlands Reloaded critters were missing derived stats. Fixed.
JPG
spite,
I'm not seeing the "centerOnToken" script error. My guess is that it is an extension that needs to be updated.
Regards,
JPG
Looks like it's the enhanced images extension.Quote:
Originally Posted by Moon Wizard
Ahh that must be it, I deactivated it and didn't have the error again.Quote:
Originally Posted by Zacchaeus
More on my Defeat Markers on Savage Worlds:
I always get a "Script Error: [string "scripts/manager_tokenmarker.lua"]:118: attempt to index local 'tokenPlaceholder' (a nil value)" when I delete a token with the Defeated markers option on.
It even happened to me while I was a recording a video showing 3.20 new features for combat, I forgot to turn off the Defeater Markers and the error popped up. ( https://www.youtube.com/watch?v=8hjpH1SBVo8&t=26m30s ).
I have two computers home, one I usually leave on Live version and never mess with the files my wife just uses it to join games I host. Since I've already got problems with Defeated Markers that only seemed to happen to me in a very weird scenario, I updated my other computer to 3.20 and the same error did happen.
Contacted Ikael and he told me it's running fine for him and said it had to do with the 'transparent_1x1.png' that was moved from SavageWorlds to the CoreRPG ruleset.
Just checked everything and re-download both rulesets (Core and SW). No extensions enabled, no folders with content just the pak. It didn't work.
Extracted both to folders, checked that in fact the transparent_1x1.png was actually there and the reference to the token "ruleset/CoreRPG/tokens/transparent_1x1.png" was correct. Everything was placed where they were supposed to be, but it didn't work.
Then I moved the transparent_1x1.png back to the SW Ruleset and changed the reference to "ruleset/SavageWorlds/tokens/transparent_1x1.png" where I put it and... it worked.
I don't know why it doesn't work when it references to CoreRPG, but it does work if it's in the same place but inside SW Ruleset.
One computer runs win7 and the other win10, both 64-bit. Both use Steam for download and updating, both use the \%appdata%\Fantasy Grounds directory because I just got used to it. This is the only relevant info I can think right now.
More on this: So I turned off my computer and then for some reason it stopped working. I reverted it to initial setup (transparent_1x1.png on CoreRPG and referenced there) and... It started working as it should.
I thought I was crazy, booted up my other computer and it still had the same error. I tried the fix and it didn't work. Then I tried to do one thing I did on my PC: the /reload command. After that, it did work. So basically the /reload fixed my bug. On my PC I tried to revert the transparent_1x1.png to the SW ruleset, and opened FG again and it did not work. I typed /reload and voilá, the defeated markers did work again.
So I don't know if this is a bug or not, but I think I found a way to fix it on my computers.
Edit: Ok, so I got the error and fix on video so it's better explained: https://youtu.be/i-FZsbmPWAw
After this, I went on my other computer loaded SW and it did give me the error as expected. I didn't touch anything, just typed /reload. After reload the Defeated Markers were working.
Sometimes it stops working again, I just type /reload and it works once again.
Updates
- Ruleset defined tokens not loading. Fixed.
Yep, that'll do it.Quote:
Originally Posted by spite
Everyone: please keep this in mind when reporting issues - if you're using extensions try to recreate the error without any extensions loaded. If you get the error without any extensions loaded then please report it here (for v3.2.0) or the ruleset specific thread, if you don't see the issues without any extensions, then it's probably an extension you're using that's causing the issue. Check the extensions you're using for ruleset compatibility - for example, I'm not aware of many available extensions that have been tested/updated for FG v3.2.0 test (only one that I'm aware of). Then load the extensions one-by-one to see which extension is causing the issue. If you find which extension it is, then post in that extension's thread - not in the base ruleset/laboratory test thread. Thanks.
For the record, all the DOEs have FGv3.2-compatable versions, but they have not yet been released and won't be until FGv3.2 itself is released.