A major version update that doesn't break the rendering system !
Did Mojang finally grow tired of making useless random changes in the code ?
A major version update that doesn't break the rendering system !
Did Mojang finally grow tired of making useless random changes in the code ?
In one sense, it belongs to Microsoft now. In a much bigger sense, it’s belonged to all of you for a long time, and that will never change.
Quote from hardcorerobot
So I can't make money selling my photographs if I use Photoshop?
Your argument is at best facetious.
Quote from Kabis
To those of you saying "If I make a mod I'm not allowed to sell it". You are allowed to sell content that you have made. If YOU wrote a bukkit plugin you are allowed to sell it. It doesn't matter if it relies on Mojang's code or not. Minecraft relies on Microsoft's or Apple's code. With out their OS Minecraft wouldn't be able to run! But Mojang can still sell their game with out being sued by Microsoft or Apple you can sell your code with out being sued by Mojang... That's how it works. Say you write a plugin that displays very nice particle effects over bow shots. You can sell that to players in game.
Quote from Minecraft EULA »
Modifications to the Game ("Mods") (including pre-run Mods and in-memory Mods) and plugins for the Game also belong to you and you can do whatever you want with them, as long as you don‘t sell them for money / try to make money from them. We have the final say on what constitutes a tool/mod/plugin and what doesn‘t.
Quote from citricsquid
Yes! That is the worst bug in the world and it's completely resolved on the new platform, also a brand new feature is included called "Revision History", Revision History allows you to see every previous edit to your posts and you can revert back to any of them at any time.
Feel free to play around with this feature in the "Test" section of the beta forum, make a post, edit it, refresh the page, edit some more, then use the "Post History" drop down to see everything!
Quote from mg127
you still don't get it ^^
when mojang really does it the way i think it will happen, then you will reach the 4k ID limit only when you have all those block mods active at once on your client, that means 4000 active modded blocks oO
when i used the term "minecraft" i didn't mean mojang, i meant the CLIENT or SERVER, the ID-register-table is only LOCAL on this one world on the server, other worlds may have other register-tables
e.g.:
server A:
uses: mod1, mod2
mod1 has 2 blocks, registered on next free IDs 257 and 258
mod2 has 1 block, registered on next free ID 259
...
mod1 gets an update, a new block, this will now registered with ID 260
client a:
joins the server, downloads world-informations, downloads ID-register-table from server A
gets the information that mod1:block1 is 257, mod1:block2 is 258, mod1:block3 is 260, mod2:block1 is 259
server B:
uses mod3, mod1
mod3 has 3 blocks, registered on next free IDs 257, 258, 259
mod1 has 2 blocks, registered on next free IDs 260, 261
mod1 is on both servers, but with different IDs registered!
Quote from Funkytron
I normally play vanilla 1.6.2 at 80 frames. On amplified i run at almost 300. What the crap?
1
See all those duplicate lines ?
You installed Battlegear twice. Check everywhere under your mods folder.
And latest version for 1.7.10 is at 1.0.8.4.
0
You tried to install Shaders on an Intel card. Pretty sure it doesn't work at all. Remove the shader stuff.
You other issue is you watched Youtube videos. They are always going to be uninformative, out of date, or simply wrong. Just don't go to youtube for information regarding anything. For each mod, seach this forum for the topic it was created in, then follow the installation instructions one by one.
Go to files.minecraftforge.net for latest Forge download.
0
From the code at the top, only use #iterator() once, or you'll just have an infinite loop.
0
There is a huge difference between 1.8.9 and 1.10.2 there.
1.8.9 had the bow models hard-coded in RenderItem.
You'll want to override Item#getModel for your bow because even extending ItemBow will not be enough.
0
Baubles-1.10.2-1.3.BETA7-deobf.jar
Deof jars are usually not for players.
0
ItemStack#getItemUseAction() may be able to weed out some cases.
To get fancier, you'll have to use reflection to check whether the item class has "onItemUse"/"onItemRightClick" overriden method.
0
Your first three cases never happen in normal game situation.
The problem is that player.getHeldItemMainhand() returns null if empty hand.
0
I would recommend
git fetch
git merge branchname
To ensure you get the chance to fix any conflict over the diffs.
0
You have wrong implementations for 4 methods out of 5 in your recipe class.
I'd suggest fixing them before complaining about bugs.
0
You don't have to uninstall. Just install the version you want and change the profile launcher setting to use that version.
1
Git keeps track of the changes for each commit. When you switch branch through 'git checkout', the changes on the old branch are 'undone', while the changes on the new branch are applied.
Thus, as long as you commit all the changes you intend to keep, git checkout will 'unplay'/'replay' them when appropriate.
If you think the changes in a 'test' branch are good enough to include in 'master' branch, you use 'git merge <test>' to apply them on the current branch.
0
Write setter method that store the drop item as field in your common class. Override the vanilla drop method using this field.
You can call the setter after everything is initialized and registered.
0
Yes by default ItemStack NBT is sent from server to client.
If your "ingredients" are items in slots, you only need the container, not custom packets.
0
Minecraft has a concept of "local difficulty", calculated from Chunk#inhabitedTime, which is the time players have spent within a chunk.
You could use this to have mob spawn areas of higher "level". Just like spiders can spawn with potion effects through it.
Alternatively, you could leave common world spawning to "low level", and rarily spawn "high level" mobs around "high level" players.
It would help to despawn them when far from the "high level" so that "low level" players don't accidently run into them.
0
http://minecraft.gamepedia.com/Skin#Creating_a_skin