Forien's Copy Environment

[muted sedge]

Seems not to be working? Hitting import knowing the things that should change, does the reload, things aren't changed. Was working prior to updating to v13

@cosmic depot
Sorry if ping unwelcome/unneeded. I'll run tests with Find the Culprit, see if it's a module conflict, but wanted to drop the note here in case it's not just me

[muted sedge]

Yeah, it's enabling the modules, but a second import is not bringing in the sub-settings for those modules like it normally does

Ran Find the Culprit, still happened with nothing else on

[cosmic depot]

Thanks Morgan - I’ll try get to checking it later this week/next

[muted sedge]

Any luck reproducing, or just a me thing?

[muted sedge]

@cosmic depot

[cosmic depot]

I haven’t had a chance to yet sorry. Work has been flat out. Please keep reminding me though ❤️

[muted sedge]

All good, hazards of maintaining something that doesn't give much back. For what it's worth, I love it and it's my single biggest saving grace as someone who runs 7+ games a week, thank you for developing it/keeping it alive

[cosmic depot]

Looks like I've got it working again. It was due to the html structure change of the setting sidebar in v13.

You weren't getting this far at all were you @muted sedge ?

[muted sedge]

Don't think so. Basically, I could do the first import, and it would activate the right modules. But usually, if I imported again, it would bring in the per-module customized settings. It wasn't doing that second step correctly. I'll test in an hour or so to see if it's doing it right now

[cosmic depot]

I haven’t released this version. I’ll keep digging

That doesn’t sound like what I fixed

[cosmic depot]

Hmm - I think Foundry might be blocking the module from being able to set configuration settings while those modules are not (yet) enabled (they only appear after the refresh)

This is the updated module.js file though, for the couple of fixes that I did make

So after updating, choosing the Export Settings option does nothing?

[dusk ocean]

Oh, the option of it does what it needs to do(creating and saving the export settings json file). But trying to import it does nothing. Importing the json file created by save as json works and causes the options menu to pop up, but attempting to import the export settings json file does nothing. Which used to be the case for both before. But the update has fixed it for the save as json file.

Basically step by step: 1. Click save as JSON. JSON file is saved to my hard drive. Click import settings. Select JSON file. Open. Menu pops up about the options and all that. Fully works. 2. Click export settings. JSON file is saved to my hard drive. Click import settings. Select JSON file. Open. Nothing happens. No menu or anything.

[cosmic depot]

Hmm, I’ll have to have another look at it tomorrow

[dusk ocean]

Salute!

[cosmic depot]

Should all be working correctly now @dusk ocean with the current release #package-releases message

[dusk ocean]

Updated, oddly still a no go for me. Exported the settings, attempted to import, nothing happens.Head scratchWhat is it about my world that is breaking it. I'd assume it's one of the other modules, but when I made the fresh test world I turned on all of the modules and it worked in the test world. My next attempt when I have the time will be making a copy of my world and "re-installing" it and see if that does the trick.

[dusk ocean]

The update to 2.1.3 did it! Works splendidly. Thank you so much for all the hard work, and sorry if I was driving you crazy! @cosmic depot

[cosmic depot]

Woohoo!