<!-- 
RSS generated by JIRA (9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13) at Sat Jan 11 07:49:36 UTC 2025

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>Mojang Studios Jira</title>
    <link>https://bugs.mojang.com</link>
    <description>This file is an XML representation of an issue</description>
    <language>en</language>    <build-info>
        <version>9.12.2</version>
        <build-number>9120002</build-number>
        <build-date>10-01-2024</build-date>
    </build-info>


<item>
            <title>[BDS-9824] Unable to join world sometimes when using imported level.dat files.</title>
                <link>https://bugs.mojang.com/browse/BDS-9824</link>
                <project id="11700" key="BDS">Bedrock Dedicated Server</project>
                    <description>&lt;p&gt;Some worlds won&#8217;t let players join when using imported level.dat files. When the level.dat files are swapped out for ones that the server software made itself, even when keeping all the other files the same, everything works fine and players can join.&lt;/p&gt;

&lt;p&gt;The reason I said &#8220;some worlds&#8221; is that I didn&#8217;t have this issue with another world I imported. I think this has to do with the size of the world, the smaller one worked fine, but I haven&#8217;t tested this.&lt;/p&gt;</description>
                <environment>Ubuntu Server 20.04.1 LTS</environment>
        <key id="386224">BDS-9824</key>
            <summary>Unable to join world sometimes when using imported level.dat files.</summary>
                <type id="1" iconUrl="https://bugs.mojang.com/secure/viewavatar?size=xsmall&amp;avatarId=18903&amp;avatarType=issuetype">Bug</type>
                                    <status id="5" iconUrl="https://bugs.mojang.com/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="7">Invalid</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="Banaantje04">Sarah van de Noort</reporter>
                        <labels>
                            <label>awaiting-response</label>
                    </labels>
                <created>Sun, 15 Nov 2020 21:16:01 +0100</created>
                <updated>Wed, 18 Nov 2020 02:35:38 +0100</updated>
                            <resolved>Wed, 18 Nov 2020 02:35:12 +0100</resolved>
                                    <version>1.16.40</version>
                                                            <votes>0</votes>
                                    <watches>1</watches>
                                                                            <comments>
                            <comment id="842831" author="ionicecko" created="Wed, 18 Nov 2020 02:35:08 +0100"  >&lt;p&gt;Thanks Sarah.&lt;/p&gt;

&lt;p&gt;Unfortunately, as I mentioned, there is no supported scenario where you should be swapping out level.dat files. Doing so is manually modifying core files which always has dangers attached.&lt;/p&gt;

&lt;p&gt;If there is a specific missing feature that is causing you to want to swap the level.dat files out I would suggest heading over to the feedback website (&lt;a href=&quot;https://feedback.minecraft.net&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://feedback.minecraft.net&lt;/a&gt;) and proving that specific feedback to remedy the root problem.&lt;/p&gt;

&lt;p&gt;If there is in fact an official need to replace the level.dat please feel free to comment back and the report can be reviewed.&lt;/p&gt;</comment>
                            <comment id="842664" author="banaantje04" created="Tue, 17 Nov 2020 21:57:26 +0100"  >&lt;p&gt;The world in question already had a level.dat that was swapped out. It could be that swapping it again fixed it. Personally, I have never had issues when switching level.dat files so I don&#8217;t know how bad this issue is.&lt;/p&gt;</comment>
                            <comment id="841604" author="ionicecko" created="Mon, 16 Nov 2020 02:45:38 +0100"  >&lt;p&gt;The level.dat has information regarding the world database and as such is not interchangeable.&lt;/p&gt;

&lt;p&gt;You may find that sometimes it works (which is likely an indicator that the two world versions were very similar) but there is no supported scenario where you should be moving only a level.dat file between different world databases.&lt;/p&gt;

&lt;p&gt;Unless there is a supported scenario I&apos;m not thinking of this would be invalid due to manual changes to core files.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                <customfield id="customfield_10500" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Confirmation Status</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10300"><![CDATA[Unconfirmed]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_11700" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_11600" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i1oc7z:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                    </customfields>
    </item>
</channel>
</rss>