- #Minecraft more player models 2 update
- #Minecraft more player models 2 skin
- #Minecraft more player models 2 download
Originally I thought that since those are addons, there's no need to modifiy the default Steve/Alex model, so that one would be unmodified. Hello, first of all I'd like to thank for all the replies(unfortunatley still had the default Github notification settings, but that should be fixed now).
So you need a server that delivers the data. And you have to know the IP-adress of these clients, which is a bad idea because of privacy and safety. The server you play on can't be used for temporally storing the data, because optifine is only a client mod.Īnd sending the data directly to the other players is also a bad idea, because you probably have to send the model stuff very often, which is bad for the ping. it would mean a lot of traffic for the model-server, because every time you join a server, you sent the model-information and it would also need a certain amount of space because as long as you are on a server, the model-data has to be stored, because maybe you come into the range of another player who doesn't have your model-data.it would reduce your ping, especially when your upload speed is very low.Sending the model to a server while joining is a very bad idea: So if you want to enable custom player models here, optifine has to host all the skins/models (and the client request the data like it does for capes) and that would need a certain amount of storage, so it might be necessary to restrict uploading models similar to capes.
#Minecraft more player models 2 skin
If your client receives this data, it request the skin form mojang's skin-server. So if you are on a server and another player comes inside your view-range the server notifies your client and sends you the playerinfo-packet, with the data it got from mojang during the login of this player. And because optifine is only a client mod, it can't change hitboxes and similar things (server side-stuff), so that won't allow cheating.īut the only way to change skins at the moment is to upload them on mojang's skin-server.
#Minecraft more player models 2 download
This is the Concept I came up with, should work in theory, not sure how difficult the implementation of the Netcode would be but I do imagine that it would work, in a way this would also be similar to the skins available in the console edition(as far as I know, every game copy does have those stored locally) working in a similar way and probably make it the easiest way to implement those than to have players download player models and animations. If the other player(s) doesn't/don't have the resource pack, your regular Skin and Model gets displayed If the other player(s) has/have the resource pack, your picked player model gets displayed. Player Joins the Server, on join the info of the other skins gets requested and your info sent(I guess this is also how the Mojang Skin system works, your skin gets sent to the other Clients who "download" it while you "download" the other skins): The way this is supposed to work would be the following: Use Default Model (useful if you have "just" a retextured skin in the pack so you don't need to have copies of the default player model, this might need a Steve/Alex toggle) Use Default Skin (useful if you have a slightly altered model that's compatible with the default skin, like for example a smaller player model like the Child Zombies, and want to allow the player to continue using their skin) In said properties file, there's also following flags: properties files, having their display name and model file name, maybe a tiny bit of lore text, one line or so) from the resource packs get listed, in resource pack order or Alphabetical(maybe we can also have a toggle for that but this doesn't need to be in the original implementation) Here is where the fun stuff starts, the custom models(which I guess could be defined in some.
#Minecraft more player models 2 update
Steve and Alex are there to help texture pack artists, those can have some good use there to quickly switch and test skins instead of using the Mojang site(which seems to not update skins if the texture file has the same name or has even further delays due to cache) Steve (default Steve Model + Steve Skin from the Texture Pack)Īlex (default Alex Model + Alex Skin from the Texture Pack) In said Menu, you see the following list(with scroll bar and preview on the right) :ĭefault (your default MC Model+Skin from Mojang) In the Options, or under Skin Customization you'd have a new menu called "Skins". Hello, I hope this isn't unwanted, but I just came up with a little concept on how we could have custom player models: