LexManos

Then post logs of it crashing with "NO" mods.

I'll look into it, however, we do not modify anything related to view distance that would cause this, and if it is a issue it would be in vanilla. How are you editing the view distance? What values are you setting it to? How are you tracking these 'abandoned chunks'?

Hidden is spoiler that's what ti does. Gist is also fine. Anyways this is caused by your client thinking where you are placing is inside your range, but the server disagreeing. This can be easily reproduced by finding somewhere you have to jump to place a block above your head. It'll sometimes place and sometimes disappear. This is just the nature of being on the EDGE of a range and being slightly desynced from the server. There really isn't anything we can do about it, nore is it Forge's fault. Now if you come back with a specific in-world reproducible manor that is notably different between Forge and vanilla that I can debug then i'll look at it, but looks to me like you're just desyncing.

Going to opt to not help you there, there are to many closed source launchers that could potentially be malicious. There is no reason to be closed source when working with users credentials. Locking the thread this time because you're not getting my point, we do not support 3rd party launchers, we do not endorse ANYTHING closed source when related to Users credentials. The fact that you can't launch Forge correctly just shows that you have no idea what you're doing considering you do the EXACT same thing for vanilla that you do with Forge.

We do not support 1.6.4 especially developing for it. Update.

Why not just use arrays? ModelBase[][] stages = new ModelBase[max_id][max_stage]... Could even cache the result of stages[id] in the TE so that it doesnt have to pull out from that every render frame.

Update to 1.7.

Going to opt to not help you there, there are to many closed source launchers that could potentially be malicious. There is no reason to be closed source when working with users credentials.

Read the EAQs

Use the standard setup -.- ALL resources are copied into the resulting jar -.- So if you tell it your source files are resources it'll copy them. Separate your resources from your code, as we have in the example mod.

1) Those are not obfuscated names those are unique SRG names 2) The 'modder friendly' names are supplied by the community to get to work. Welcome to minecraft modding, this is just a thing of life. As for not being able to read the source, it is there, you can read it, you just cant MODIFY it. And you can EASILY find references of anything. So, learn to your use IDE better I guess. We have superior functionality to 1.6, All of the things that were named in 1.6 are still named in 1.7, the things that are GONE are GONE not renamed or anything stupid like that. *notes renforcment of lack of attention to detail.*

Then speak to the modpacker, We do not support old mc versions.

Ya that is saying you don't have internet. Perhaps you have a firewall or something blocking you.

Try loading it up without ANY mods. Something appears to be corrupting random classes related to rendering things.

You need internet to install Forge as it downloads files. If you DO have internet, run it manually as shown in the video in my signature and post the logs here.

Do not make 1.6.4 packs, 1.7 has been out for 9 months, use it.

How did you 'export' the jar. If you did it through your IDE that is wrong. Just run gradlew build Your assets DO NOT go in your src/main/JAVA folder that is for JAVA files They go in src/main/RESOURCES/ as they are RESOURCES.

Really... really... Anyways support for 1.6.4 is no longer given on these forums, 1.7 has been out for 9 months, there is no reason to NOT update.

If build fails what makes you think it'll work in the client? Get the full log from the build script including the stack trace like it tells you to. You're trying to be a modder, you should know how to follow directions given to you by errors.

Seriously this is not hard and if you would actually try it you would see. Edit the Game directory. Simple as that Question Answered.

Update to 1.7.

Your launcher is broken and doesnt properly load the versions of the libraries we need.

Update forge, you're running the single version {1191} that has a snight metadata bug, it *might* be what's causing your issue. However, the other potential is that you're lagging somehow. What it looks like is the server thinks the doors are closed but your client thinks they are open. {And vise versa for the buttons} So update, and see what happens.

We have a block break and interact event, use that.

One or more of your mods is a client only mods. Sadly the trace doesnt tell us which one so you'll have to do a little digging.