Why are people still coding for 1.7.10/1.8?

[nocot]

Is there a significant case that is making so many people stay with such obsolete Minecraft versions? Is that because of compatibility with some old mods or what?

[DaemonUmbra]

Some people refuse to give up their favorite mods from back in the day, they would rather live in the past and demand that mods be backported rather than find new favorite mods in modern versions

Some modders are in that camp and others fall to peer pressure from that camp.

There are also those who hated the combat update with a passion and refuse to accept the change.

[Hangy]

Personally, 1.7.10 will always have a special place in my heart. While I was a beta player, I never really got into modded until 1.7.10. That being said, I was one of the people that was very resistant to the combat update, but I came around eventually. New mods and packs eventually won out, and here I am on the bleeding edge with the rest of what I used to refer to as "the crazies". Some of my favorite packs of all time are back on 1.7.10, and I don't think that's likely to change any time soon. Outdated, sure. Obsolete? Not hardly!

[Cadiboo]

6 minutes ago, Hangy said:

Personally, 1.7.10 will always have a special place in my heart. While I was a beta player, I never really got into modded until 1.7.10. That being said, I was one of the people that was very resistant to the combat update, but I came around eventually. New mods and packs eventually won out, and here I am on the bleeding edge with the rest of what I used to refer to as "the crazies". Some of my favorite packs of all time are back on 1.7.10, and I don't think that's likely to change any time soon. Outdated, sure. Obsolete? Not hardly!

It should be noted that the code for those mods has been obsolete for almost 3 years

[Cadiboo]

Just now, Cadiboo said:

It should be noted that the code for those mods has been obsolete for almost 3 years

Correction, more than 4 years old

[Hangy]

27 minutes ago, Cadiboo said:

It should be noted that the code for those mods has been obsolete for almost 3 years

I wasn't trying to argue semantics as much as show some love for 1.7.10, however, "obsolete" is defined as "no longer produced or used". While yes, it's no longer being used by Mojang in their current releases (at least not in its entirety), the code is still being used by "lazy modders" and too many players to speculate on an actual number. I would then submit that it is, by definition, not obsolete, just old.

Edited August 27, 2018 by Hangy

[IlTosaerba]

Basically, 1.7.10 version is the best version to use in custom forge servers with friends.

It's not only my opinion, we done a test and if 1.8.9 or 1.12 are the most powerfull ones, 1.7.10 still the best if you don't have a server and want to host a VPN to play with your friends.

Crete mods for 1.7.10 means create costum content for and/or with your friends.

[DaemonUmbra]

2 hours ago, IlTosaerba said:

Crete mods for 1.7.10 means create costum content for and/or with your friends.

You say this as if 1.7.10 is unique in this regard.

[vpontin]

Staying in 1.7 is not only a dumb resistance for change, its a dishonest way to fool new players and (mainly) modpackers and server admins to stay with a very old version with more problems and less features.

 

Man, i will list just some amazing things for those guys Mojang introduced starting on 1.8:

- Banners and Shields (medieval hype YAY);

- Rabbits (i only miss them being tamable in vanilla);

- Polar Bear;

- Armor stands (i suffered a hell back in 1.6 when i tried to install a armor stand mod);

- Spectator gamemode (good for Hunger Games-styled gameplays);

- Grass paths (great way to make makeshift roads to ride your cool horse and guide yourself);

- Arrows with potions (very interesting mechanics);
- RESOURCE PACKS (change audio, textures, far more things than before);

- DATA PACKS (1.13);

- Loot Tables (with them adding items in loot from other mods became far more easy and acessible to pack makers, provided the mod use the system propely);

- Recipe JSON system (1.13?) (same of above);

- The whole structure system (i will talk about below);

- Command Blocks;

- Customized world type (its a very powerful mode to play);

- Buffet world type too (1.13);

- End civilization;

- SHULKER BOXES;

- ELYTRA!!!

- HERE'S JOHNNY (dont remember the name of the mob, is a blue villager);

- The fancy map related to the mob below;

- I already said Data Packs?

- OCEAN STUFF! FINALLY (1.13);

- The new terracottas (people hate it at first, but with proper handling amazing buildings can be made;

- THE FLATTENING (1.13) (It would turn things far more easier for pack makers, everything separately for me is better);

 

Dont like the cooldown system introduced by Combat Update? Here.

 

Everything became more clear and nice to tweak in my opinion. Even for mods it really impacted. Remember the old AtomycStryker Ruins mod? Vazkii made Pillar, which use the vanilla structure system and is far more easy to make than the former. There are also other examples similar in which a new replacement mod does things far less shady than their precursor and uses more the available vanilla systems (perharps NEI > JEI can count).

 

There only a small couple of mods i lost, but i would say its more because of Bukkit drama and shutdown than the 1.8 transition: TrainCarts (i still waiting for someone to make this), perharps Lockette (but Vanilla introduced a way to lock chests already), the permission system (althourgh i dont play multyplayer enough and with so much people to actually require it) and any mod to change the Villager models to Humans (i think today this would be a violation of EULA, but MCA is somewhat still going).

Anyway for any modder still coding only for 1.7: PLEASE dont force your players to stick with a version so old and with so few features  Beta was good but this new versions are EXCELLENT, such amazing RPG-esque tematics for me were decisive to add a new breath to the game.

Edited August 29, 2018 by vpontin

[Kzitold]

Because some people refuse to give up their favorite dead mods and too stubborn/lazy to find clones of those dead mods for more current MC's.

[Gwolfski]

vpontin, speaking of Traincarts, that's available as a server plugin for 1.10-1.13

[digitalNacht]

Players will tend to stay with what they like when they already have the game experience they want.  If players are sticking with 1.7 at least a few modders will stick with it as well because they are likely playing 1.7 as well.  It really just comes down to personal preference.

[Cadiboo]

Personally I think the main problem is lack of Mojang's proper support for mods. If it was easy to port mods between versions, and Mojang made any of their code with modding in mind, I think that people would be much more receptive to updating to - and using the newest version.

This is why lots of people are still using 1.7, the changes between 1.7.10 and 1.8 were massive for any even slightly advanced mods. The amount of work that had to be done to port the 1.7 mods to 1.8 was so much that many modders gave up and stopped modding altogether. (Most of) This could all be solved if Mojang gave us a Modding API, as Forge is just a bunch of (very good) bandaids covering a wound that has existed for almost a decade now.

1.9's changes to combat saw many people stay in 1.8, even though there are (now) mods out there that allow players to use the old combat system.

Edited September 23, 2018 by Cadiboo
added link

[larsgerrits]

 

15 hours ago, Cadiboo said:

If it was easy to port mods between versions, and Mojang made any of their code with modding in mind

This is why the last few updates have been so big code-wise. They're trying to do make updating easier between versions by remaking their old systems.

[Animefan8888]

15 hours ago, Cadiboo said:

This could all be solved if Mojang gave us a Modding API, as Forge is just a bunch of (very good) bandaids covering a wound that has existed for almost a decade now.

Mojang however has outright stated that Forge is better than anything that they could make, though this was a while ago. But the Java edition as of now(presumably ever) will not get a Modding API. There are plans for bedrock edition to receive a Modding API.

[Cadiboo]

46 minutes ago, larsgerrits said:

 

This is why the last few updates have been so big code-wise. They're trying to do make updating easier between versions by remaking their old systems.

Which absolutely breaks every existing mod so were kinda back where we started

[LexManos]

Things have to break in order to get better. Its just something that people have to deal with.

Objectively the java Minecraft engine has gotten better in all the recent updates.

There is a reason why Forge doesn't port old things to the new versions even tho tons of people complain.

Because once they see the changes they realize they are good.

Mojang is not concerned with the between-version updating. They are concerned with the engine itself.

Holding themselves back because it might inconvenience modders is not what they should be doing.

 

Anyways, at the end of the day people can write for whatever they want, but the community AS A WHOLE, should move forward and keep up with the current version.

1.13 is being a major challenge, but hey it's worth it.

[Guest]

That's because 1.7.10 and 1.8.9 are the best versions. Most people who demands mods for those versions are only the Minecraft PvP Community people, and they only want client-side modifications.

 

 

Any version above 1.8.9 is trash. As of now.

 

[DaemonUmbra]

10 minutes ago, D0XY said:

Any version above 1.8.9 is trash. As of now.

On 8/25/2018 at 10:45 PM, DaemonUmbra said:

There are also those who hated the combat update with a passion and refuse to accept the change.

A common theme I see among fans of old versions is the tendency to push that their favorite version is the "best" version and that their opinion is somehow factually proven, rather than their opinion.

[vpontin]

On 9/22/2018 at 5:34 PM, Gwolfski said:

vpontin, speaking of Traincarts, that's available as a server plugin for 1.10-1.13

 

I know but there isnt any way anymore to make spigot work with forge, like Cauldron back in 1.7. Also i'm very reluctant to add yet another "API" prone to crash or clash with mods (Sponge), so thats why one day i will be very happy if someone makes a "native" Forge mod adding that funcionality.

 

 

2 hours ago, D0XY said:

That's because 1.7.10 and 1.8.9 are the best versions. Most people who demands mods for those versions are only the Minecraft PvP Community people, and they only want client-side modifications.

 

 

Any version above 1.8.9 is trash. As of now.

 

You really doesnt read my reply above. Go for it before vomiting such things.

[Guest]

On 9/24/2018 at 9:17 AM, DaemonUmbra said:

A common theme I see among fans of old versions is the tendency to push that their favorite version is the "best" version and that their opinion is somehow factually proven, rather than their opinion.

I know it's not a fact, but the PvP community thinks the same, "every version above 1.8.9 is shit"

 

On 9/24/2018 at 11:51 AM, vpontin said:

You really doesnt read my reply above. Go for it before vomiting such things.

Those updates don't make up for the combat changes and block hitting animations and all those stuff we miss. You'll never change my mind about what's the best version, I still think 1.7 / 1.8 is. Everything above those are shit and are only for SMP or Survival servers.

[vpontin]

Okay, but with this mentality and language you will not have any support here i think...

[Merkk]

On 9/25/2018 at 7:59 PM, D0XY said:

I know it's not a fact, but the PvP community thinks the same, "every version above 1.8.9 is shit"

 

Those updates don't make up for the combat changes and block hitting animations and all those stuff we miss. You'll never change my mind about what's the best version, I still think 1.7 / 1.8 is. Everything above those are shit and are only for SMP or Survival servers.

That's a cool opinion you have there. What a shame it's only an opinion.

1.13 is in my opinion a much better version of Minecraft than 1.8 in its entirety.

[vpontin]

2 hours ago, Merkk said:

That's a cool opinion you have there. What a shame it's only an opinion.

1.13 is in my opinion a much better version of Minecraft than 1.8 in its entirety.

Keeping your server playerbase playing a 4-year-old outdated version because of "PVP" BS (instead of just using the mod i've linked to revert the combat) is at the verge to be dishonest, there's a lot of features you are denying them to play because a single "issue".

[TheRPGAdventurer]

It's sad that some of my favorite mods in 1.7.10 are left and abandoned one of my favorite abandoned mods is Dragon Mounts, you can hatch the ender dragon egg and tame it as your own, it's a bummer minecraft had a dragon egg item yet you cannot hatch it, Dragon Mounts didnt have firebreathing and dragon armors before, but the ability to hatch the dragon egg was more than enough, when it was abandoned, I learned java myself and updated it as my own then added firebreathing and dragon armors on it.