#KASPER ISSUES

1 messages · Page 1 of 1 (latest)

proud ibex
#

@forest wyvern if you can, can you run these two commands in your console and paste me the objects.

game.settings.get('kasper', 'storage'); and game.settings.get('kasper', 'presets');?

I think something is off with one of those and casuing you an issue. I am not sure what it is though.

forest wyvern
#

let met launch and find out

proud ibex
#

whelp we found the issue

forest wyvern
#

v10 vs v11 maybe?

proud ibex
#

Let me take a look and downgrade to v10. I really shouldn't be an issue, it looks like the presets isn't getting registered, any chance you are getting an error when loading foundry?

forest wyvern
#

checking

proud ibex
#

Which is what makes this interesting. If I sent you a zip, would you be willing to override your kasper files with it for testing?

#

Actually I think I know what it is, looking at your image.

#

I think when regestering a setting I do config: game.user.isGM, and this seems like the issue, because you don't have this setting on your issue on github.

forest wyvern
#

same error happens with your zip

proud ibex
#

Can you send it to me, so I can get a better idea of which line

#

nevermind

forest wyvern
#

warning above it prolly matters:

#

Also players can't see the existing Kasper data:

proud ibex
#

You have to right click and show it to them.

#

But it looks like your context menu option is broken

#

But the data looks right?

forest wyvern
#

yep its all fine works as it did in 1.0, was updating purely for the show to players functionality though hehe

proud ibex
#

I can fix the context menu, I just want to make sure you didn't loose any data.

forest wyvern
#

yeah everythings solid and intact, plus if I think about it, I have a backup of it from last sunday

proud ibex
#

Alright, well give me a bit and I'll see if I can quickly patch this context menu issue too. If so I'll ping you to test if thats okay

forest wyvern
#

yep I'll be around!

proud ibex
#

It might be tomorrow, I think I have to ask a dev for support. It appears the logic for binding a ContextMenu is different in v10 then v11 and from some reason v10 is saying this.element.on is undefined.

#

I will do my best to fix it first as soon as possible and let you know.

forest wyvern
forest wyvern
#

@proud ibex with your manual install version, when you first view the Kasper Manager, all the bars are full but the values are right and then if you adjust anything they all correct:

proud ibex
#

I found the issue, it looks like foundry is finally moving away from jQuery. I was passing in an HTMLElement and not a jQuery object. So a small little piece of code

// TODO: Remove this when Foundry v0.10.x is no longer supported
// ? To add support for v10, convert element to jQuery
let elem = this.$el;
if (isNewerVersion('11', game.version)) elem = $(this.$el);

If you get a chance, can you test this: https://github.com/mouse0270/kasper/releases/download/1.1.2/module.json

#

if that works for you, then I will push the release out on foundry's admin portal.

forest wyvern
#

oh woops, hang on let me go fix things, I forgot I was installing a v11 headless instance on my server and dropped my v10 while it was busy.

proud ibex
#

I messed up my comment it looks like. should read

TODO: Remove this when Foundry v10.x is no longer supported

Not worth pushing an update now though. haha