I just copied the error from the log, dunno what to tell ya. :confused:Quote:
Originally Posted by SilentRuin
It pops up in the error console whenever I try and drag a new monster into the list of available polymorphs for Shapechange.
I'll do some more testing and see if I can puzzle out what's causing it.
I have a suspicion that it's the character sheet that is causing the problem - it is a very old sheet, and has been used in a game for like, 5 years. It's possible it's accumulated some garbage clauses or something from being modified, and perhaps they are messing up Poymorphism's expected behaviour...
Quick way to verify is to remake it.
I was in fact correct; remember kids, make sure to keep up with your house-keeping :pQuote:
Originally Posted by SilentRuin
Heya! So I've actually encountered the exact same error message about sTargetType and recreated a brand new character sheet following the 2024 ruleset and I'm still in the same situation with the message appearing.
Any idea as to what else it could be ? I've got everything updated yesterday and still can't quite figure out what's going on...
Could it be a conflict with other plugins?
Thanks in advance!
Here's the screenshot with the error messages. First is when I try to activate a polymorphism (wild shape) and second when I deactivate or try to add a new NPC form.
I can't duplicate this at all. In fact, I can't tell what can be causing it. I don't use 2024 but did try it in my 2024 test campaign for druid turning into a bear with no problems.Quote:
Originally Posted by Joj0no
The code is validating the target of the polymorphism and is insuring you are not trying to turn into an NPC that is an object or item type without using true polymorphism spell. As you can see from the code below...
The only way you could get an error where sTargetType things its a number is if some massive code corruption or some of this code was overriden. The node "type" is a string - not a number. But your error is claiming its a number. I am curious about what happens when a "" would come back for sTargetType - so will fix that section to make sure it is "undefined". Not sure how that would interpret as a numeric.Code:...
-- most things (not consistent) have a type
local sTargetType = DB.getValue(nodeTarget, "type", "");
if not sTargetType then
sTargetType = "undefined";
end
...
-- an object can only be used by true polymorph
if sFilter ~= Interface.getString("polymorph_filter_TruePolymorphSpell") and ((sType:lower():find("object") or sType:lower():find("item")) or
(sTargetType:lower():find("object") or sTargetType:lower():find("item"))) then
...
I don't even know how that is possible with my code as written.
My suggestion is that you remove all extensions but polymorphism and try this again. It should work unless your data is truly something I have no idea how to duplicate. If it does work then you have to add in half your extensions - try again - if it fails with that half then their is conflict with one of them - if it does not then its in the other half - you just keep narrowing it down till you find it.
Unless you can tell me 2024 has changed some core DB type schema defintion in the last few months I have no way to fix or know what is going on. Its unique to your data/extensions I suspect.
Only if I can duplicate it would I be able to fix it (with my extensions and my data). Other peoples extensions and odd data I can't really track/fix. Nor do I attempt to.
I'd also check what NPC you are trying to turn into and what its "type" is defined as - as that seems to be the issue. Whether it is the data or some other extension stomping that data - I have no idea.Quote:
Originally Posted by Joj0no
This is a good mod but at this time I see one thing that could be fixed there is a new up date but this bug was in for some time when you morph and you are in 2d/3d view the person/monster image go's to a token and not the portrate.
I'm not sure what you mean. If you have the 3 images of the NPC defined that you are polymorphing into then that NPC will have those images. If you do not - then it will not. As far as what is displayed - it absolutely only handles the token image as a token. I'm not even sure how the 2d/3d decides to use which image. But the code only deals with the token image. Any other of the 3 images you wanted to use would have to be put into the token. But really I've never done anything but the token on the 2d map. Never envisioned special support being required for 3D - I would assume whatever the NPC had defined would be what was used.Quote:
Originally Posted by Xealot
I get this error on the latest version of FG when trying to drag an NPC onto a druid PCs character sheet as shown in the video. Attachment 65915