LexManos

Either 1) Stop using 1.5.2 or 2) Follow the eaqs

Holy jesus tits, stop using Mod makers... Makes for horrible code. This is a obvious error to anyone who has delt with mods. Protip: Toss a debug line in you'll see the error straight off. Either way, gunna guna help anymore until you show you're not using a mod maker

Console logs would probably help. However, it sounds to me like your setup can't handle 512x for some reason, and btw 512x is FUCKING HUGE, why in gods name would you need that much ? I'm gunna guess at most your screen is 1900x1600, which means you can see 4x3 blocks on screen at that resolution anything high is just silly.

No, if you're using linux you should know how to run what you need if it doesnt work on your system. Beyond that, we're not using python in future versions.

If its a MCPC issue, go to the MCPC forums. None of your setup is under our control.

Stop using 1.5.2

Because cpw decided to make it severe. And if you're getting it in your dev console, you should update and fix it.

Meh, there really isnt much need for a special wrapper around an array list. The functionality is fairly basic, just a couple of loops over the list. Also, a note about your implemnetation: 1) It breaks compatibility with anyone who reads the list from the field. 2) It should of been submitted in a Pull request 3) Please be a bit more efficient in your implementation. Only one lookup is needed. A single map.get(key) instead of hasKey, get, put, over and over.

SAP_ManPackCore_v200a.jar Seems to be broken with your configuration it can't find where it wants to patch, try removing it.

Either way this isnt our issue. To run Forge you run the forge jar Simple as that We cant help you beyond that. Multicraft if this is what you're referring to is a control panel. You need to do some research into how to change the jar that you're running with that control panel.

And then destroy compatibility with ANYTHING that reads network packets? Seriously guys, it's not jsut a matter of 'strip that downcast' These types of changes have a LOT of implications and compatibility issues with things that are outside of our control.

Interesting, something in your setup is keeping a reference to the world after it's marked to be unloaded. It's not Forge doing that, but it is Forge trying to notify you. Best bet would be to try and track down specific mods that cause it. As for the stack, thats caused by something in your save file, holding a entity that is in the wrong chunk... Thats a rather odd one again, there are many causes so not sure, However, it tries to correct itself so you should be ok unless its happening A LOT.

1.5.2 != 1.6.4 We do not support 1.5.2 anymore, My only advise, read the posted tutorials or update to atleast 1.6.4

Welcome to MC modding And yes, im pretty sure it's sent as a byte over the network.

Wow my bad, did not notice that commit.. I blame the con flu! Interesting. Will keep an eye on things, but working on gradle first.

IIRC last I looked into it, we dont due to network communication.

No clue what prints those out, this is not Forge. One of your mods is trying to police the other mods. And probably won't work. Not our issue.

Ya I dont know what the fuck you're doing wrong but entities do NOT need a global registration. As things are picked up for you already when you do the mod registration as long as you DONT fuck it up by doing the global registry. But ya, banned cuz you're just being a cunt. The class is fairly fine if you read it. And as evidenced by the code snippit I pasted comments DO exist. Anyways have fun, be less of a cunt, enjoy modding!

/** * Register the mod entity type with FML * @param entityClass The entity class * @param entityName A unique name for the entity * @param id A mod specific ID for the entity * @param mod The mod * @param trackingRange The range at which MC will send tracking updates * @param updateFrequency The frequency of tracking updates * @param sendsVelocityUpdates Whether to send velocity information packets as well */ public static void registerModEntity(Class<? extends Entity> entityClass, String entityName, int id, Object mod, int trackingRange, int updateFrequency, boolean sendsVelocityUpdates) { instance().doModEntityRegistration(entityClass, entityName, id, mod, trackingRange, updateFrequency, sendsVelocityUpdates); } Humm humm yes that is SOOOOOO FUCKING CONFUSING!!!!! Note what it says about the id:MOD SPECIFIC ID Cuz you know.. id conflicts between mods are stupid and shouldnt happen. Hence Mod specific... Either way, don't be a fucking cunt. The id issue isnt OUR issue. It's a Minecraft issue that we have had resolved for ages. The ONLY reason the global ID BS is there is for MODLOADER compatibility and it's going aweay in 1.7

For note: 1) Minecraft.com is NOT minecraft's website, minecraft.NET is. Minecraft.com seems to be some actual mineing company IRL. 2) That seems to be a REALLY old REALLY early version of the 1.6 beta launcher. This is what the current launcher looks line: Oh I see what the issue is, you're one of those people who are pirating Minecraft! You're using 'SimpleMC's launcher which is nothing but adware/crap. Ya gtfo off our forum.

Yes as I said I was talking about the Launcher. Not the installer. The Launcher you are using is old, you should use the newest mojang launcher from there website. Linked in the post above mine.

Where did you get that launcher? Thats not the vanilla launcher, thats the a really old version. Use the normal launcher.

2013-11-06 13:23:05 [sEVERE] [Minecraft-Client] Using missing texture, unable to load: minecraft:textures/blocks/MISSING_ICON_TILE_500_StrongStone.png You have to set your texture name -.-

What you SHOULD do is move to the normal per-mod spawning mechanics. Which uses a modid + mobid combo to allow you have compleetly seperate ID set and not cause any conflicts, overflow, etc.. We will not "fix" this as you're doing it wrong. See the EntityRegistry in FML.

Jesus guys he posted the fucking log the first time, quit being dicks. It doesnt HAVE to be pastebin. Anyways the issue is you didnt actually stop the server, and it still locked the files. Make sure to kill the process, Delete session.lock and try again. But it looks like you've derped up your world somehow by not shitting down correctly. Always make backups!