Leaderboard

just read your own post again.. if it outputs you as name : tile.ruby_block.name then it would not be block.ruby_block.name=Block of Ruby change it to tile.ruby_block.name=Block of Ruby and it should work hope that helped

Don't compare string instances using ==. Use the equals method.

Well, since RenderPlayerEvent fires every time the player is rendered(aka every frame) you are adding a new layer each frame...

Pulled together this from existing EAQs and multiple peoples signatures. It still needs input because, a lot of it has not been updated since 2013.

Love Forge so wanting it faster I started to help with 1.13. Suggestions: Updated the Rules and EAQs in Support with which versions are completely unsupported, so someone like myself can reply that it is no longer supported and take some of the load off. The same with any other updates if needed. Testing is currently all I can do to help directly, I am familiarising myself with the 1.14 release (very hard work in vanilla ? ) currently so I will know what is normal. Being able to know what you expect to be working, and don't, would be very helpful, I can't yet read PR well enough to understand what the effect of many of them will be. So a rough run sheet of what has been altered recently would help focus testing and then when it is ready for the full test, ie placing every block, braking every block, finding, taming and breeding every animal and so on. Also I am learning Java through edx.org Microsoft: DEV276x (still can't believe I am doing a MS course or another programming language) but I am working through the usual hiccups of different versions. Some tips about what versions will be used in 1.14 and beyond would be appreciated. My preference is for written documentation and I am willing to help consolidate and/or put some together. I have found and gone through a lot of documentation on forge in the last 6ish months. Kind regards Sana

A sample replacement EAQ

Another possible update - the "old" (1.6.89-j) official Minecraft launcher will no longer work with current versions of Forge.

So one question, two replies and two different answers. I know enough of the people involved to be pretty confident the answer is currently 1.11 & 1.12.2 & going forward is expected to be 1.12.2 & 1.14x. But the overarching rule of the forum is don't answer anything you don't know for sure. Is there a problem with updating the EAQs?

1.14 is probably going to be special, 1.14&1.12.2