Links
Tags
Creators
Details
7.1.6
Compatibility
Changes
Easy Shop Mod 7.1.6
š§āš¼ļø Player Faces System Update
-
ā Player Faces Issue ā Resolved with Manual Setup:
-
The player faces issue has been resolved, but to work correctly, a manual step is required.
-
š Required Setup:
-
Each player must:
- Install the mod
- Launch the game at least once
- Place their skin file (
.png) inside the following path:
\config\Easy Shop Mod\My Skin
-
-
š¼ļø How it works:
- The mod will automatically read the skin file from this folder.
- Your face will then be displayed correctly to all players without issues.
- Any other player who places their skin in the same path will also have their face displayed correctly.
-
ā ļø Default Behavior:
- Players who do NOT place a skin file will appear with the default Steve face.
- Until they add their own skin.
-
š Important Requirement:
-
The skin must be:
- 64Ć64 resolution
-
This is currently the only supported format for correct rendering.
-
-
ā ļø Notes & Limitations
-
ā No Automatic Skin Fetching:
- Automatic skin fetching is currently not available.
- This is the only reliable solution at the moment.
š Apology & Explanation
-
I sincerely apologize for not noticing this earlier.
-
š Reason:
- The mod was not tested on a real multiplayer server.
- Multiple approaches were tested but did not work reliably.
- This manual method was the only stable solution found.
š Additional Info
-
If the folder:
\config\Easy Shop Mod\My Skinis empty, the mod will notify you to remind you to place your skin.
š¬ Final Note
- Thank you for your understanding and support ā¤ļø
- If you have any suggestions or find a better solution, feel free to share it on GitHub.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:U4fXl7jN:tmgwjUdi"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:U4fXl7jN:tmgwjUdi"
}

