Regenerate player data files

Oct 13, 2025 by talynt.org 120 views

[1.21.1 Bug]: Custom Skin Newborn Stage Not Appearing on Server

As a dedicated server owner, it can be frustrating when bugs arise that affect the overall experience of your players. In this case, we're dealing with a custom skin newborn stage not appearing on a server running Dragon Survival 1.21.1 with NeoForge 21.1.128. The issue seems to be specific to the server, as it doesn't occur in single-player mode or when all mods are present in a single-player world. In this article, we'll delve into the details of the bug, explore possible causes, and provide a solution to get the custom skin newborn stage working again.

The custom skin newborn stage is not appearing on the server, while the young and adult stages are fine. The glow layer seems to work on the Newborn stage, but the skin itself is not visible. This issue is only happening on the server, and it's not present in single-player mode or when all mods are present in a single-player world.

The modpack being used is Casualbox 1.21.1-March 9 2025, which can be downloaded from the provided link. The server IP is k23universemc.playit.gg, and players can test the bug by joining the server.

There are a few possible causes for this issue:

Mod conflict: The issue might be caused by a conflict between mods on the server. When all mods are present in a single-player world, the issue is not present, which suggests that the conflict is specific to the server.
Dragon altar usage: The user mentions that they switched from an adult griffin to a dragon using the dragon altar, but they're unsure if this is related to the issue.

The user has provided two log files:

latest.log: This log file is from the client side with all mods present.
2025-03-09-6.log: This log file is from the client side with possibly conflicting mods removed. The bug is still present in this log file.

To resolve this issue, we'll need to investigate the possible causes and try to identify the conflicting mod. Here are the steps to follow:

Analyze the logs: Review the provided log files to see if there are any error messages or clues that can help identify the conflicting mod.
Disable mods: Disable each mod one by one and see if the issue is resolved. This will help identify the conflicting mod.
Regenerate player data files: Try regenerating player data files to see if this resolves the issue.
Test on a single-player world: Test the modpack on a single-player world to see if the issue is present.

The custom skin newborn stage not appearing on the server is a frustrating bug that can be resolved by identifying and removing the conflicting mod. By analyzing the logs, disabling mods, regenerating player data files, and testing on a single-player world, we can resolve this issue and get the custom skin newborn stage working again.

For those who wish to test the bug on the server, the server IP is k23universemc.playit.gg. If you're able to reproduce the bug, please provide any additional information that might be helpful in resolving the issue.

Casualbox - 1.21.1-March 9 2025.zip
latest.log
2025-03-09-6.log
[1.21.1 Bug]: Custom Skin Newborn Stage Not Appearing on Server - Q&A

In our previous article, we explored the issue of the custom skin newborn stage not appearing on a server running Dragon Survival 1.21.1 with NeoForge 21.1.128. We discussed possible causes, including mod conflicts and the usage of the dragon altar. In this Q&A article, we'll answer some common questions related to this issue and provide additional information to help resolve the problem.

A: The cause of the custom skin newborn stage not appearing on the server is likely due to a mod conflict. When all mods are present in a single-player world, the issue is not present, which suggests that the conflict is specific to the server.

A: To identify the conflicting mod, you can try disabling each mod one by one and see if the issue is resolved. This will help you narrow down the list of mods that are causing the conflict.

A: Some common mods that can cause conflicts include:

Modpacks: Modpacks can contain multiple mods that can conflict with each other.
Custom skins: Custom skins can sometimes conflict with other mods that modify the dragon's appearance.
Behavior mods: Behavior mods can modify the dragon's behavior and sometimes conflict with other mods.

A: To regenerate player data files, you can follow these steps:

Stop the server: Stop the server to prevent any further data from being written.
Delete player data files: Delete the player data files from the server's directory.
Restart the server: Restart the server to generate new player data files.

A: Yes, you can test the bug on a single-player world. This will help you determine if the issue is specific to the server or if it's a general problem with the modpack.

A: The server IP for testing the bug is k23universemc.playit.gg.

A: Yes, you can provide additional information to help resolve the issue. Please include any relevant logs, screenshots, or other information that might be helpful in resolving the problem.

The custom skin newborn stage not appearing on the server is a frustrating bug that can be resolved by identifying and removing the conflicting mod. By following the steps outlined in this Q&A article, you can resolve this issue and get the custom skin newborn stage working again.