![traincraft 1.9 traincraft 1.9](https://i.ytimg.com/vi/6r0ZqjON7-Q/maxresdefault.jpg)
Not to mention the way the mod is managing this stuff is just about the only way to do it because of how minecarts and fluids are dealt with. I think all we really need to do in relation to packets is make our own Packet250CustomPayload class, and everything else, for the most part, should easily just fall into place.Īnother thing is that a rewrite may not even be necessary after this port works, it looks really bad, but in reality, cleaning this up is mostly just refactoring and removing redundancies/unused features. This tutorial gives A LOT of relevant information on the networking stuff. Just re-applied my changes and submitted it again. You have to add each one individually, then in the list make sure they're ticked.ĮDIT: Not quite sure what happened but my commit didn't appear to get sent to the Github repository.
Traincraft 1.9 plus#
If not, on the right click the plus button then select "JAR or directories.". If they're there, edit them to point them to the correct file in the dependencies folder. then select the Modules tab, and in the list on the right (probably at the very bottom) should be the added references to the.
![traincraft 1.9 traincraft 1.9](http://79.170.40.162/minecraftdls.com/wp-content/uploads/2013/10/diesel-trains-minecraft.png)
In IntelliJ, load up the Traincraft project then go to File -> Project Structure. Here's what I did just in case it hasn't fixed it.
![traincraft 1.9 traincraft 1.9](https://i.imgur.com/AyAS6AZ.png)
Try getting latest now to see if it's sorted it out. My hope is that it uses relative paths for things in the /lib folder. I've just tried moving those files into the /lib folder to see if that fixes it for you, as I think maybe it's using hard-coded paths to the dependencies at the moment which won't match up on your machine. With the dependencies, you've probably seen but I added a "dependencies" folder in the root. Reorganized my replies too, rather have one big one.Īwesome, glad you got it working on your machine. This will probably effect where your changes get uploaded, so be sure it's all setup right on your end. Heads up, I moved the default branch for this fork to one named 1.7, to make things more clear for the people on the main project. Including the errors from dependencies not being imported correctly, there are 596 errors, most of which seem to be rather repetitive. I'm gonna need help on that if you have any idea. Now the issue is getting the dependencies (buildcraft, ic2, etc) to work. I uploaded the new README.md with the instructions and a number of changes to reflect where this branch/fork is going. I had to manually define the location of the JDK, and manually redirect the forge bin to the forge bin jar. It solved the issue with needing the start folder, but the :ForgeBin: error still persists. Seems to import to InteliJ quite easily just by importing the adle.įound a tutorial here to help with importing
Traincraft 1.9 mods#
One thing that may also help is that most of the errors (9.5 out of 10 I'd assume) we will encounter are related to 1.7.2, because most mod devs went there before 1.7.10, so most of the "why doesn't this work?" being asked will be towards 1.7.2.ġ.7.10 was only a bugfix and the addition of Realms, which shouldn't effect mods much, if at all. It's also the hardest task so its best left for after we have a bit more experience with the API from fixing other stuff. 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.
![traincraft 1.9 traincraft 1.9](https://i.ytimg.com/vi/-mtcoRR_APk/maxresdefault.jpg)
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:
Traincraft 1.9 code#
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: