Minecraft Forums

I came to this thread thinking it is very difficult to take seriously a troll face. But you do have a few posts already under your belt. So who knows...

Answering your question, it is perfectly fine to release a buggy, slow, even crashy, snapshot. It's the nature of these updates to be unfinished releases the community can play around and spot problems that are then reported to Mojang for fixing. The whole point is to test the new or changed features before a full release.

My thought exactly. "Technically" is the sort of word you use to fool yourself with half-formed truths.

"Technically" the Dire Straights weren't a rock band, but a group of friends. "Technically" water flows up.

I was going to suggest it was the plugin API as a snide remark.

He was hired for it and yet seems to be working on everything except this. He even says this so-called long requested feature is a lot of work.

But no. It's not the Plugin API, it is the skins...

Hello, I need to know what are the leaves base colors to use for the multiply blend mode when trying to reproduce the leaves in the John Smith texture pack.

I'm building a full SketchUp Minecraft template (that I will publish here once it's finished for others to use) based on John Smith Texture pack. In order to correctly model the blocks in 3D I need to create the textures myself. For the most part I use the textures given in the resource pack. But some blocks textures are calculated at runtime and the only thing in the resource pack I have access to is a greyscale source for a blend mode.

I managed to solve this problem with the grass by using the grass colormap file (colormap\grass.png) to extract the grass source color (R137 G166 B75). But the foliage colormap file (colormap\foliage.png) is multi-colored and I don't know what colors to extract.

Base colors needed:

• Acacia Leaves
• Oak Leaves
• Birch Leaves
• Spruce Leaves
• Jungle Leaves

Quote from gerbilfat

Registered here to post this - Norton is flagging and automatically deleting the .exe version.

If you can, uninstall Norton from your computer. You'll be doing yourself a big favor.

Norton anti-virus and the related competition (Panda, McAfee, Kaspersky, AVG Internet Security, et cetera, basically anything that qualifies as an internet security suite) are notorious for:

• giving false positives.
• Clogging your computer memory with unnecessary bloat.
• Demanding too much processor time.
• Allowing all manner of virus to still creep in because these antivirus are obvious sources for attack.
• Conflicting with all manner of other software and crashing, freezing or otherwise compromising your computer ability to serve you. As is the case you just experienced.

There is no reason today to use this type of software, especially considering most of them are subscription based, when you have much better (this is no exaggeration) completely free anti-virus software out there. Internet security is pretty much dealt with by your operating system these days. The Windows firewall, for instance, is a good tool in its own right, while if you need true control you can adopt much lighter and more powerful solutions to Norton, or any other of the names mentioned above, with port-based software firewalls.

As for the anti-virus the best (again no exaggeration) solutions out there are all completely free and much more benign to your computer. And of these, perhaps the best one is Microsoft's own Security Essentials.

That report you got from Norton is a false positive. The AMIDST is well and good and highly recommended. It's Norton that sucks and it just shown it to you by stopping you from using a perfectly good piece of software.

Indeed. Maybe another time and another quiz which doesn't require me to disclose personal information.

Quote from WitherSnow

How old do you think lefty is?

That question wasn't directed at me, but let me just say this is pretty irrelevant. In a forum environment, where age is even an optional field in your profile, it's hard for anyone to make behavioral judgments based on age.

On the other hand, it's not even a good thing to do. It's judgmental in more than one way, because it implies you steryotype based on age. When in fact, people of all ages can display all forms of good or bad behavior. Two different people could be 13 and 31 each, and still display the same good or bad behavior.

I prefer to attribute behavior to a personality trait. And I suggest you do the same.

Quote from PopuliMinistrum

And as I said, in my post which you apparently neglected to read, that is because they rewrote a lot of code, including the rendering engine. If they had started on the Mod API in the main branch then modders would already be able to see traces of it. So while they are paving the way in the main branch so when it is completed they can add it without issues, they are not working on it in there.

The new naming mechanism that broke mod support in 1.7.2 has nothing to do with the rendering engine. And if it did, Mojang would have a serious dependency problem on their hands, like few I ever saw on a game programmed in a OOP language.

It seems to me you are a little green on these matters and are just arguing for argument sake, You are free to go on, if you want. But you are just being a distraction from the main discussion.

Quote from IronMagus

Forgive me for being n00b, but what's the difference?

None much in the context of Minecraft. They were just being pedantic.

If you want to know about the semantics of both words, a mod may imply no support from the main program, meaning it hacks its way into the program in order to change its behavior (they modify the program). Whereas a plugin always implies direct support from the main program that has the necessary programming hooks that modders can use to change its behavior (they plug in to the program).

But in the context of gameplaying, you will rarely address a mod as being a plugin. Just feels weird, and will get a few laughs, to say Thaumcraft plugin, or that Azanor is a pluguiner, instead of a Azanor is a modder.

Quote from PopuliMinistrum

You must be a little new here, mods break with every update because the game code is changed and therefore the mods are compiled over old code and have to be re-written.

You have to be new here if you think that is the same of what happened in the 1.7.2 update. In case you didn't read it, or forgot, let me remind you. the 1.7.2 update broke all mod support by changing core aspects of the game that invalidated all the previous work on MCP. This only happened once before that (the version of which I can't remember). And the reason for this was explicitly said by Mojang to pave the way for the plugin api. Every other update in Minecraft history, since MCP was first released, never compromised MCP for more than a few days.

They keep making villagers sell more and more interesting stuff, don't they. A few more updates and the only thing villagers will sell us will be rotten meat.

*sigh*

Quote from DanSparrow

Don't expect it to simply be out because they wont release anything without it being as perfect and useful as they can make it

I feel I need to clarify something here to you and a few others, because my main doubt that anything is happening around the plugin api has exactly to do with what we are seeing, instead of what we are not seeing.

If what you say were to be true, that would mean they are working on the plugin API on a separate branch from the main trunk (the main source code they compile to give to us). This would allow them to keep working on the plugin API code without showing it to us and making it better and better until they were ready to release.

But that isn't what we have seen with 1.7.2. On that major update, they broke mod support in order to pave the way for the plugin API. Up until 1.7.4 we have no mod support. And we shall see what happens with 1.7.8.

The mod support breakage that happened in 1.7.2 means their work on the plugin API is being done on the main trunk. If they were working on a separate branch they would have no need to break mod support right until they were ready to release the API. But where is this work? With every snapshot since then, nothing is shown. All the game new features are related to other work, not the Plugin API.

Quote from PopuliMinistrum

The main issue is that people expect them to just drop any updates and work only on the Plugin API until it is done. it is not going to happen, and to expect it to is both unreasonable and flawed in logic.

I'm sure you'll find very few people thinking that, Populi. In over 3 years of Minecraft, I rarely saw anyone expecting Minecraft to just develop one feature and leaving everything else. Not sure why you would think that is what "people" think on a regular basis.

And some of the people in these forums are software developers themselves with long years of professional experience. It's just common and advisable practice for a team to divide work. Programmers work on a focused area and only give a part of their working day to general development, helping others in their own areas or working on less code intensive issues.

I don't know how correct I am when I say that I don't see that focused development happening at Mojang. But there's a whole lot of hints that is exactly what is missing. Even you perceive their daily routine as such.

I find your Jeb quote out of context too. They inform us a whole lot about progress development in many areas. Heck, they are tweet addicts, almost all of them. If there is one thing I can't accuse Mojang of is shunning their community in terms of what they inform about their work.

And this is precisely why the whole Plugin API (bolded as a service to the semantic nazis) is becoming a bit of a concern. Like others I think it's just not a priority anymore. It makes little sense to me that such a feature -- until sometime ago hailed so important to the point of breaking all mod support with the introduction of 1.7.2 -- is practically unknown to the players.

I don't think they are lying about it, as OCrapaCreeper implies I'm accusing them of. They are simply not announcing this feature or showing much progress towards its completion. It seems to indicate very little work is done around it, especially when we consider all the other coding activities the team is engaged on. So that brings doubt about it being really done and whether or not they have lost much interest in it.

With MCP and Forge nearing completion (or so we hope), it seems we will have to stick to a third party for mod support for a long while more.

Is anyone else concerned we never, or rarely ever, hear about this part of the development in the snapshots since 1.7.2?

Dinnerbone is said to be the one developing this game feature. He was in fact hired for it. But all we see of him is general bug fixing, dealing with the many issues with the rendering engine, and writing daily countless tweets about whatever.

Where are the bullet points about the MOD API since 1.7.2? You can probably count them with the fingers in just one of your hands?

Quote from Divinius

But you are the first to raise holy hell if they delay a snapshot by 6 minutes, or have the audacity to not be working on exactly what you want them to, when you want them to, as hard as you want them to.

Hehe. And don't forget his reaction when someone else criticizes the game. They are the complainers and the haters.

One important quality -- and social advantage -- is to be consistent between what one does and what one says. But lefty has nothing to do with it.

Quote from DaBiggman

Careful now, the Moderators here LOVE lefty

I think it's not so much they love him. It's more that he is so stupidly irritating sometimes that he ends up bringing the worse in the people that attempt to reply to him. He's an hate magnet.

Quote from Leftypower123

Third of all, I know what I want - new ores. -Lefty

And I don't want new ores. So what does this leave us? What you want or what I want?

What this means Lefty is that what you want isn't reason enough to be all worked up. It would be ok if you had some manner of saying on exactly what goes on Minecraft development, like working at Mojang and getting angry because your team wouldn't be working what you wanted. But as a player, you are just like millions of others (including me) wanting this or that and having to accept what they are given. You can surely complain, but throwing a tantrum just makes you worse than the haters you seem to see everywhere.

And why on earth new ores? What do you plan to do with these new ores? The only reason ores exist in Minecraft is to provide the source material for crafting recipes or other game mechanics. Can you direct me to the thread where you explain exactly what ores you would like and what they would be used for? Or is this just one of your's "I want stuff!" childish cries?

So you are complaining because they are keeping their promises.