So from the title you can probably guess this is about the lack of major mods such TE, Buildcraft, IC2, and Railcraft as well some other semi major mods.
So it has been a few months since 1.9 has been released and for the first mod it seemed pretty normal but after a while it seems that like (Here comes a bunch of baloney) modding just died like just out of the blue! And I'm curious as to why are the major mods are not being porting or taking forever, Now at this point I should say that I have been in the modding community since 1.6.4 and never got see most of porting to 1.7.10 as well I heard something about everything needing JSON files and stuff and etc. But my question is What is the culprit behind the prolonged delay of major mods?
You do have a valid point there well for 1.8 the thing is why there almost barely any mods were ported is because by the time 1.7.10 was done porting 1.9 was already on the horizon but that was a year later and now we have 1.9 out and for my opinion this even if 1.9 come obsolete the mods will still be ported over to ease porting on the next update which I doubt that would be a thing especially with all the things going on with servers and overhauls but its a possibility!
1.9 mods will come soon, probably. Forge 1.9 is very new in comparison with older versions, we need some improvements and stabilizations in the API to port mods for this version securely.
The time for porting from 1.7 to 1.8 is much more higher than 1.8 to 1.9 because of obvious reasons.
I'm working in a "considerably big mod" since Forge 1.8.0 (now running in 1.8.9), and it will stay in 1.8.9 until the Forge API acquire a """better state""".
Largest file loaded is 90K commands from a command_block.
Lasted Updated Aug 7 2016 ... 1.9 to 1.10.2 Also the BlockDumpMod gives blockdump command which writes blocks to a text file as execute setblock commands or gives a report.
So from the title you can probably guess this is about the lack of major mods such TE, Buildcraft, IC2, and Railcraft as well some other semi major mods.
So it has been a few months since 1.9 has been released and for the first mod it seemed pretty normal but after a while it seems that like (Here comes a bunch of baloney) modding just died like just out of the blue! And I'm curious as to why are the major mods are not being porting or taking forever, Now at this point I should say that I have been in the modding community since 1.6.4 and never got see most of porting to 1.7.10 as well I heard something about everything needing JSON files and stuff and etc. But my question is What is the culprit behind the prolonged delay of major mods?
<--- This happens too much :/
You do have a valid point there well for 1.8 the thing is why there almost barely any mods were ported is because by the time 1.7.10 was done porting 1.9 was already on the horizon but that was a year later and now we have 1.9 out and for my opinion this even if 1.9 come obsolete the mods will still be ported over to ease porting on the next update which I doubt that would be a thing especially with all the things going on with servers and overhauls but its a possibility!
<--- This happens too much :/
1.9 mods will come soon, probably. Forge 1.9 is very new in comparison with older versions, we need some improvements and stabilizations in the API to port mods for this version securely.
The time for porting from 1.7 to 1.8 is much more higher than 1.8 to 1.9 because of obvious reasons.
I'm working in a "considerably big mod" since Forge 1.8.0 (now running in 1.8.9), and it will stay in 1.8.9 until the Forge API acquire a """better state""".
Mods follow forge refactoring follows minecraft refactoring.
Writes the CommandRunnerMod which gives the executefile command to read commands from a file. http://mods.curse.com/mc-mods/minecraft/246088-commandrunnermod
Largest file loaded is 90K commands from a command_block.
Lasted Updated Aug 7 2016 ... 1.9 to 1.10.2 Also the BlockDumpMod gives blockdump command which writes blocks to a text file as execute setblock commands or gives a report.