Modding this way was not easy, either for the programmer or for the end user, who had to master the art of unpacking jar files and inserting the provided modded jars.... not something that gamers are normally encouraged to learn or do.
Eventually, some bright lads came up with the idea of a standard mod loader, that would automatically load those modified classes as Minecraft launched, so that the end user didn't to do surgery on their game executable. They also decided to solve the other problem, that if two different mods modified the same base class, you'd have a mess.
They created an API for modding, so that mods would play nicely with each other, and have a standard interface with which to mod Minecraft. That combined mod loader and API is called Minecraft Forge. Originally, you had to do surgery on your Minecraft executable to install Forge, though it would then handle all the other mods, but the Forge guys got tired of explaining how to do that, so they wrote an installer to do it automatically, and the rest is history.
So, I write mods using the Forge API. At some point, Mojang (the developers of Minecraft, now owned by Microsoft), decided to start cleaning up the internals of the game to make it easier to write mods and other add-ons. This necessarily required large internal changes, which made modding across major versions... interesting. Players who don't write mods have little-to-no idea about this, and just want to know "have you ported your mod to 1.8 yet?"
Repeat ad nauseum for every single major version change from 1.6.4 => 1.7.10 => 1.8+ => 1.9.4/1.10.2 => 1.11.2 => 1.12.2
Not ONE modder I've ever heard tell about likes being nagged about porting code. Not one. Fortunately most forum moderators figured out a long time ago that "When are you going to port your mod?" is 99% of the time, a passive-aggressive way of demanding that you hurry up and port your mod, and so forbid the question. One, it is rude and entitled to demand that modders work for you for free, and two, annoyed modders have been known to quit modding. Or put explosive bees in their mods.
So don't do that.
After I boiled a Seeker to death and recorded the results, I got another Classic Starscream and disassembled him (will document that another day). I took him apart a bit more thoroughly, so that parts like the legs wouldn't have air chambers in them and float around in the dye. I also left out parts that did not need dyeing; those that needed painting got sprayed with a light gray primer instead.
After my last experience, I was paranoid about exposing the parts to heat....
( Cut to avoid inflicting pics on everyone's friends page )
Tip: Classic figure paint comes off with alcohol and vigorous rubbing. Just take a cotton ball soaked in rubbing alcohol to it.
Washed it, and then put it in a pot of dye and water, enough to cover the parts plus an inch or two, and boiled it for about 45 minutes. (I wanted it dark). I'd been assured this was pretty much S.O.P. for dying toys.
Well, apparently the Classics figures are a bit sub-standard on the heat sensitivity. My Seeker figure had two noticeable parts warp and partially collapse from the heat of the pan that if I can put it back together, it won't transform. One leg is sort of squashed and won't collapse to transform to jet mode, and the back plate of the torso piece is a bit collapsed and warped along the right top--won't close properly for either mode.
It also came out darker than I wanted. Fortunately, I found another Classic Starscream over at Toys 'R' Us. I'll try cold dyeing that one.
Tip: DON'T BOIL Classic Transformers
Edit: Now I have pictures.