-
December 9th, 2025, 21:55 #281SmiteWorks
Supreme Deity
- Join Date
- Mar 2007
- Posts
- 23,349
Since we have not heard back from the third party developer in some time; I went ahead and made the changes the @crleonhard suggested for the last few items. Please run a new Check for Updates, and let me know if still an issue.
Regards,
JPG
-
December 9th, 2025, 22:51 #282
I updated and I think it works, based on a couple quick tests. The spells are still grayed/blacked out, but I was able to target and roll without generating an error code.
-
December 10th, 2025, 00:08 #283
The issue with the grayed out spells may be that when you first drop a new spell on your sheet it doesn’t have any available castings — try double-clicking the Rest button and see if that fixes it.
-
December 16th, 2025, 02:47 #284
Starting and Expert talents for the Faun and Halfling ancestries are blank.
They have a title on the ancestry sheet such as "Quick Step (Faun 0)" but when opened the talent sheet is completely empty.
No title, no label, no description or text.
Both ancestries are from the "Demon Lord's Companion Player" module.
Unloading and reloading the module does not restore them.
6 blank/empty talents with no label show in the Talents window under Demon Lord's Companion Player.
-
December 16th, 2025, 19:31 #285
I've confirmed the issue and put in a bug report for the Companion module.
-
December 18th, 2025, 14:18 #286
I will look into this over the Christmas holidays.
-
December 20th, 2025, 06:10 #287Devotee
- Join Date
- Mar 2020
- Posts
- 8
Hey everyone. I am running into a problem with many of the character sheet and combat rolls prompting errors. every time I make an attack roll, or any check for that matter, I get this error that is in the screenshot. Is there a work around or should I chalk this up to another broken (and useless) module? Thank you in advance and happy gaming.
image_2025-12-20_010923657.png
-
December 21st, 2025, 15:37 #288
-
January 7th, 2026, 18:33 #289
I found a bug causing finesse weapons to not apply boons/banes from effects. The fix needs to be made in campaign/item_weapon.xml in two places in the scripting for the "attack" control: line 341 (in BoonBaneCalc) and line 544 (in BoonBaneCalcNoTarget). In both places, a fix might look like this:
if nodeWeapon.getChild("finesse").getValue() == 1 and nodeWeapon.getChild("attacktype").getValue() == 'melee' then
local nFinesseBoon, nFinesseBane = 0, 0;
if nMelee > nRanged then
ModifierStack.addSlot("Melee", nMelee);else
nFinesseBoon = nStrengthBoon;
nFinesseBane = nStrengthBane;
ModifierStack.addSlot("Finesse", nRanged);end
nFinesseBoon = nAgilityBoon;
nFinesseBane = nAgilityBane;
nExtraBoon = nExtraBoon + nAttackBoon + nFinesseBoon;
nExtraBane = nExtraBane + nAttackBane + nFinesseBane;
(Let me know if you'd like a hand maintaining this ruleset; I'm happy to help.)
-
January 7th, 2026, 18:40 #290Dominic Morta
Ruleset Developer
Smiteworks
How to zip up your campaign if the Developers ask for it-How to zip up your campaign if the Developers ask for it
How to provide an Unity Connection issue?-Connection Issues and What to Provide
Unity Updater issue?-Updater Issues
Classic and Unity Port Forwarding?-Fantasy Grounds Connections Explained
Comcast or Cox ISP User?-Comcast XFinity and Cox Users
Have a suggestion?-Feature Request
Thread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)

Reply With Quote


Bookmarks