Tags
Creators
Details
1.2.0-pre1
Compatibility
Required content
Changes
OfflineSkins Reloaded 1.2.0-pre1
This is the major pre-release 1 of the upcoming 1.2.0. This version for minecraft 26.2 includes a lot of changes which will make your life better.
📂 Features
-
VoreZCore - a new core for OfflineSkins Reloaded. The core of 1.1.0 (1.1.1) was changed to VoreZCore, which is a new standard for OfflineSkins Reloaded. The core is still in beta, but in newer updates, any bug that is found will be fixed.
-
Full Custom Server Support - Version 1.1.0 (1.1.1) had a massive hole in compatibility with custom servers, but now you can fully use this in the game very quickly
-
⚡Optimization - lots of bugs were fixed
YetAnotherConfigLib(YACL)
Now you are able to manually change the config of OfflineSkins Reloaded by simply opening the Config Menu.
The mod now requires YACL as the main config library mod
🌍 More Translations
Added 3 times more translations for any life situation
KeyBinds
Added 'U' key to open configuration menu
Commands
- OfflineSkins Reloaded has 2 main commands (they are useless in your game, just keep in mind).
/offlineskins version
Shows OfflineSkins Reloaded Version
/offlineskins menu
Shows OfflineSkins Reloaded configuration Menu
⏹️ Added Buttons in the Title and Pause Screens to quickly open the configuration menu
Added more control over HD skins and capes
If you somehow got the skins from flawed 1.1.0 you may see too many people with HD skins in your game, if you were playing on third-party non licensed server. If your internet is weak that may cause internet bottleneck and highest ping. Now your problem is solved! Now you can allow or prohibit them on non-licensed servers and if someone has an HD skin, it will be replaced with a red Steve exclamation mark.
🔒Network Optimization and security
the network with custom servers was optimized and got more secure options.
- Skins and capes often don't support HTTPS protocol and HTTP is more commonly required, but if your custom server can provide skin or cape by HTTPS use HTTPS instead of HTTP.
-
In the Configuration menu you can allow or block HTTP
⚠️ IMPORTANT ⚠️
If you don't know which custom server you are getting skins or capes from, only use HTTPS! Because of security terms and your PC safety, but on trusted custom servers you can allow HTTP
⚠️ Content Warning ⚠️
OfflineSkins Reloaded may load skins and capes from third-party services. Third-party services may contain user-created content that can be provocative, offensive, disturbing or otherwise inappropriate. This content is not controlled, moderated or endorsed by the OfflineSkins Reloaded project. Use third-party skin and cape sources at your own discretion.
Build - 26.2
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:jwBsp59y:5TPfX4WE"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:jwBsp59y:5TPfX4WE"
}

