This all being said I have no idea on the packet and network manager stuff for now, but I would advise to leave that stuff for last, because other things we change/fix could change what we will have to do when fixing the networking. Space Engineers is going through a similar networking transition and they basically have to remake the majority of the game, I'm terrified of what that will do to their mods. We're lucky the forge API only changed as much as it did (Although it would be worth the effort to change more if the networking worked as well as KCauldron). Minecraft has been a selfhosted server in single player for a good while now, but what happened in 1.7 was that then entire networking system was changed over to netty this made it more obvious that single player is self-hosted multiplayer due to the extra initialization time that was the tradeoff for better performance. I also found the following post which may be useful: There's a lot of stuff about Packets, Players, and the INetworkManager which seem to be because of the change in the networking code (if I remember right, 1.7 is when singleplayer mode actually became a self-hosted server?). I think this has now become .ArmorMaterial. This moved from namespace to .ForgeDirection. Here are the most common errors I can see so far when I build:
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |