Magic

Magic

190k Downloads

Spell editor ChangeMe bug

NightScythe1 opened this issue ยท 4 comments

commented

On my server when creating new spells (or anything) using the /meditor, saving and loading the config back into your world no longer creates a file of the name specified in the editor, and now only puts it in a "new_changeme" file, so spell files need to be created and added manually. Is this a known bug? I'm on 1.19.2 Paper, and Magic 10.8.4

commented

That is definitely not a known bug ... and nothing has really changed with the editor other than a recent HTTPS cert renewal.

I just tried it out on my dev server and it seemed to work fine- can you try this same session and see if it makes a "myspell.yml" for you?

> meditor spell myspell
[07:19:03 INFO]: Creating new spells.myspell
[07:19:03 INFO]: Please wait, starting new session...
[07:19:03 INFO]: Go to https://editor.elmakers.com/64hipr1n in your web browser
> mconfig load 64hipr1n
[07:19:15 INFO]: Fetching configuration...
[07:19:15 INFO]: Created file myspell.yml
[07:19:15 INFO]: Please wait while the configuration is reloaded and validated
[07:19:17 INFO]: [Magic] Will remove out of bounds entities on chunk load
[07:19:19 INFO]: WARNING: spells.gronckleegg: Invalid spell mode: cast
[07:19:19 INFO]: Finished loading with warnings

File was created as promised:

ls -l servers/survival/plugins/Magic/spells/myspell*
-rw-rw-r-- 1 minecraft minecraft 1110 Nov  8 07:19 servers/survival/plugins/Magic/spells/myspell.yml
commented

Ah i think that was my problem! Upon creating spells, I never realised you could assign a file name in the command like you did there, I've always simply used "/meditor spell" and added the filename into the editor, then upon loading it would create the file name depending on that was at the top/first line of code. Not sure why it stopped doing that- but that's on me for using it wrong!

commented

Hmm well I wouldn't say you're doing it wrong, that workflow should be fine... so consider pre-assigning the name a workaround for now, but let's leave this issue open until I can look at it more closely.

commented

Just an update- I haven't encountered this bug anymore for a couple months now