I have thought about it, but I have not looked into what it would take to put something into the Forge.Quote:
Originally Posted by Navigat0r
Printable View
I have thought about it, but I have not looked into what it would take to put something into the Forge.Quote:
Originally Posted by Navigat0r
Truthfully, it has been a while since I have used this extension. I will take a look and see what I can do.Quote:
Originally Posted by Bonkon
I started to dig into this, and it seems there are some fundamental changes the FGU that are causing issues for this extension.
Formatting I can and have fixed on the Notes tab.
The "isLocal" error message I fixed for the Host, but it still happens at the player level.
I also see some of the fields are not acting quite right For one, the Phases are not being populated.
The person who created MoreCore is fairly busy, and I get the impression it is at the sunset of its life cycle. I'll probably need to migrate away from MoreCore, maybe go to XCore, or just build off of CoreRPG. There were some pretty cool custom roll features in MoreCore that I'm not sure can be reproduced easily anywhere else.
All User.isLocal have been removed from MoreCore to the best of my knowledge.
If you want to share me the current (the one you have made changes to already) build and instructions on how to replicate the issue I can have a peek.
I personally do think that XCore is likely to be better supported going forward. What rolls/mechanics are you specifically talking about? And yes - MoreCore has way more specific rolls built in but XCore is generally easier to add new ones to.
OK - I did find a couple more... am uploading a new build to Forge just now.
Hmmmm the build wont appear in my list... will update when I can push it live.
Good Day lamorric and Damned :)
Thanks for looking into this. :)
Forge updated now.
Thx damned, that fixed the isLocal issue.
There are still 2 outstanding issues that I am looking into.
1) The script that should convert the SPD into a string of the phases a character acts on is no longer populating the field it should be.
2) The custom dice tower no longer shows. :-(
I want to poke around at #1 some more, and I have yet to look into the #2.
If anyone has any ideas why #1 might be happening, I would love to hear them.
The SPD field has script functions for onInit and onValueChanged. The onInit calls the onValueChanged. The onValueChanged function gets the SPD value, converts it into a string of the phases the PC acts on, and sets other fields with this value. The code is similar to other functions on the same page, that seem to still work. I put "print" statements in and can see that the SPD value is getting converted. It is probably something that has changed "recently" in the way the value should put into the other fields, and I am just not seeing it.
Alright,
I found the "last" issue with the Phases, fixed the custom dice tower, and have updated the extension.
I also put the extension on the Forge. Things are pending and I'm unclear how long that will take.
More about the issue for those interested.
Found a new underlying "feature" with how 'anchored' and 'multilinespacing' interact. It would cause the control to just not appear. Once I changed how 'anchored' was defined for the Phases, all was well.