-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[1.19] Configuration Migration Issues #7913
Comments
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Since I seem to have had some errors, just for completion here's my paper.yml I had before: https://paste.gg/p/anonymous/ac947dd04450483f886cbafbd9c1ecea Several settings weren't copied including the velocity-support section, anti-xray, entity-per-chunk-save-limit, max-auto-save-chunks-per-tick and a lot more that I didn't check yet. I still have to verify it with experimental build 2 once it's working :) |
@Folas1337 please post any stacktraces that may have appeared in the logs. I just ran your config through the migration and I see the velocity section (it moved, search for |
This comment was marked as resolved.
This comment was marked as resolved.
@Folas1337 are you sure? look inside the world folders. I specifically checked for that too. Like I saw the antixray settings for world_survival_nether and world_survival_the_end |
Ah alright, I take that one back, totally missed they're in the world folders. Thanks for clarifying, the other 3 are still valid though. |
Ok, async-chunks.threads being set away from -1 is a bug, and the alt-item-despawn-rate enabled being flipped is too. the 2nd one tho is supposed to happen. EDIT: @Folas1337 both of those issues should be resolved when the next build is posted. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
After trying experimental 4, one out of my six worlds did not convert properly. My backup file
But my
No console errors so I'm not sure if this report is helpful in the first place. |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as outdated.
This comment was marked as outdated.
That log doesn't help at all. Please provide the latest.log instead of the crash report. |
This comment was marked as off-topic.
This comment was marked as off-topic.
Use the latest experimental build, build 5 @heychazza |
I've verified with build 5 and can't find any errors anymore. If any configs were missing in the new file entirely I wouldn't have noticed. Might check that later... maybe someone else does before me, then feel free to report :) |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
@SirKillian can you post your full paper.yml? There should've been a backup made of it. I can't seem to replicate your issue. Setting server.properties level-name=Spawn and adding those 2 lines to a default 1.18.2 config works fine. They show up in the Spawn folder's config file in the right place. |
|
Still getting the server crash on startup with experimental v5. Log: https://pastebin.pl/view/574f1a77 |
Just to give you an update: This issue is not caused by paper! There existed a file in the directory which was called |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as off-topic.
This comment was marked as off-topic.
Resolved in 76f81ae |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
Certain fields which were configured previously as maps (and were working) are causing my server to not start, as it is looking for lists. Per the discussion on the paper forums, the 1.18.2 config was likely "invalid" but as it worked there and did not work in 1.19 after the config conversion, the experience was confusing. Maybe it can be a case where "lists" defined as "maps" could be converted as part of the conversion? The issue is resolved by changing "{}" to "[]" in the config files. Server error log:
Full log file: https://paste.gg/p/anonymous/9dc3dabf6fc748e9836b194662f22e68/files/ab36129599384284b5a87cf30258f7a6/raw Relevant section of 1.19 paper-world-defaults.yml:
1.18.2 paper.yml: https://paste.gg/p/anonymous/d54b1f2a0acb482cbfd4a9405795b670/files/e073226ec0d744fd8311c53b3903f11e/raw I made a thread about this in the forum if the additional info is helpful: https://forums.papermc.io/threads/server-wont-start-compiled-from-the-latest-git-commit-currently-d1b1c6f.359/ |
This comment was marked as off-topic.
This comment was marked as off-topic.
Nothing to do with this issue, you already have something running on that port |
This comment was marked as off-topic.
This comment was marked as off-topic.
Please go to our Discord for support. Your issue has nothing to do with what we are talking here |
Since we didn't receive any other reports for over a month now, and all the known issues have been fixed, I'm closing this. If anyone else finds a config migration issue please open a new issue. |
Please put all 1.19 configuration migration related issues as comments on this thread. Known issues will be added here.
Known issues:
packet limiter overrides are not correctly accounted for on a reobf server ([1.19] Crash on startup, config related #7911)5ac29fc02b5ec4async-chunks.threads
was set away from the auto value of-1
02b5ec4alt-item-despawn-rate
was migrated incorrectly or not at allMissing entity type entries in76f81aedespawn-ranges
causes a crash on world load.The text was updated successfully, but these errors were encountered: