Urgency?! The shady? future of modded minecraft

[iNd3x]

I don't know anything of FTB and Mojang working together, they might to some extend.
None the less i don't understand why Mojang doesn't think: "Hey! we have a community with some insane good mod developers, let's make it work together!"
To be honest some kind of teamwork and support with updating from Mojang could be a path. In the end it all comes from Mojang, Mojang owns the game -Mojang makes the choices.

-Why aren't FTB and Mojang working close together? In an official way!

 

[Hyperme]

-Why aren't FTB and Mojang working close together? In an official way!

Because as much as some people would like to pretend it's the case, FTB isn't the end-all hub of modded Minecraft.

Also:

good [...] mod drm.

lol no. I mean you can maybe argue light drm is okay for actual commercial products, but for a free mod created via reverse engineering, drm is for the fools.

Incidentally the whole reverse engineering thing is maybe why Mojang don't care about mods break. Or, more likely, they are a bunch of nerds who don't know how to run a company.

 

[RealSketch]

[DOUBLEPOST=1391358195][/DOUBLEPOST]

I don't know anything of FTB and Mojang working together, they might to some extend.
None the less i don't understand why Mojang doesn't think: "Hey! we have a community with some insane good mod developers, let's make it work together!"
To be honest some kind of teamwork and support with updating from Mojang could be a path. In the end it all comes from Mojang, Mojang owns the game -Mojang makes the choices.

-Why aren't FTB and Mojang working close together? In an official way!

They won't, FTB would be ruined, defeating the point of FTB and even though it's modded and super fun! FTB has much more bus than vanilla and requires so much more updates/permissions.

 

[Hoff]

-snip-

More of these types of posts will get this thread closed, quickly.

OT: The sky isn't falling and won't fall. People will come and go. Most of the devs that left were already openly planning on leaving. For some the childish attitude gave them reason to give their two weeks notice and others it was just coincidence. There'll be a day when cpw and Lex will leave the community. That'll be a far darker day and the sky still won't be falling.

 

[BIG mac]

Honestly, I could probably just play on the mod packs we already have for a very long time, so I don't see much point in worrying about modding drama.

 

[Bigglesworth]

I'd like to think this is all there is to it - I really would, as I often like to spout on about how "we'd all be better off if Mojang stopped updating" - but if this were really the case (modders giving up just because "Mojang's update broked things") etc

So just to check, your argument is:

• Modders are angry because the code changes each update
• Mojang are not changing the code to make way for the plugin api

Right?

No.


The issue isnt with Mojang updating things. I want them to update things. The issue is that it is done without a care that its going to waste a lot of the time the community puts into MC, when if they would just sit down and set out an API guideline that they also follow, this wouldn't happen.

There is zero sacrifice here and everything to gain for both Mojang and the community. Mojang is eroding their development community, FREE development for their game with their apathy toward it. Instead of making it easier, they are making it harder and that is a poor plan for longevity and ironic for a sandbox game.

 

[danidas]

According to what I been seeing the mod api is one of the main reasons they are revamping their code in the first place. As they are trying to clean up and refine their code so that a modding api would be practical. In addition they are only really focusing on limited areas of the code for each update. For example in one update they rewrote the sound engine, next one they did the graphics/opengl upgrade, then they did the blockid to blockname change, and so forth.

So to me they are actually trying to minimize the effect of this on the modders while also ensuring that the modding api will be the best it can be. As you cannot make a great api for poor code that was in need of a rewrite any way, at least not one that wouldn't need to be rewritten all the time . As for the reason for the poor code most of it is from tacking updates on top of each other for so long with out doing a major revamp.

Personally the whole blockid to blockname revamp that modders are currently dealing with for 1.7 is the most important/greatest change in a long time in regards to modding. As it finally eliminates the whole issue of block ID conflicts making modded minecraft easier then ever from the user stand point.

 

[portablejim]

No.


The issue isnt with Mojang updating things. I want them to update things. The issue is that it is done without a care that its going to waste a lot of the time the community puts into MC, when if they would just sit down and set out an API guideline that they also follow, this wouldn't happen.

There is zero sacrifice here and everything to gain for both Mojang and the community. Mojang is eroding their development community, FREE development for their game with their apathy toward it. Instead of making it easier, they are making it harder and that is a poor plan for longevity and ironic for a sandbox game.

So you aren't talking about:

• Players, items, events, etc. being able to be detected by commands so in the future, instead of a mod needing to dig into classes, it just might need to run a few commands. (1.4, 1.5, 1.6, 1.7, 1.8 snapshots) (e.g. backpacks in vanilla)
  
• Implementing a 'tweaker' system for mods to hook into minecraft code. (1.6 + launcher)
• Separating out textures from one large texture sheet (that you have to get the index x and y for the item to get the correct texture) to individual texture files (so you can just have named files for each texture), also allowing HD textures. (1.6)
  
• Setting up a Resource Pack system (could be called an API) in which the vanilla textures, sounds, fonts, langugage files, end credits, end poem and splash text are part of the vanilla resource pack and can be replaced by another resource pack without needing to modify any code. (Mods add their own resource pack in order to add textures, etc to the mod.... Well they should. You may see errors such as "Mod X is missing a pack.mcmeta file, things may not work well") (1.6)
• Improving the chat system and translation system. (1.6)
  
• Setting up a registry for blocks and items so that modders don't need to worry about managing item IDs themselves (1.7)

?

There are also some changes that forge softened, so that both the old and new method were available in 1.6 with the old method being removed in 1.7.

 

[Jadedcat]

I believe the moderation staff has made it more than clear that this topic is not to be brought to this forum. Take the drama back to reddit/MCF. It does not belong here.