-
Posts
9264 -
Joined
-
Last visited
-
Days Won
66
Posts posted by LexManos
-
-
You're lieing, I can tell by your stack trace that you're lieing. you have some mod somewhere that needs MLMP.
-
In theory, tcp will keep your ordering.
MC does some queueing stuff and stick map related packets on the back of the queue, and there is always a chance that some other thread fucks up your packets.
Your best bet would be to verify that it's reassembled correctly on the other side.
-
-
Install MLMP, however, you should tell whoever made the mod to stop using MLMP as it is dead for all intents.
But when you do install it make sure you install it first, so that Forge overwrites all its classes properly.
-
Do not use config/{mod_class}.cfg That is for MLProp
Use your own name in config/
-
Its in the main download, under *latest*
-
Id believe you if it wasn't blatantly obvious that you're lieing.
*points at your error*
-
I think the hard limit by MC even with the few bug fixes that FML does, is 128x, so if you want higher, install optifine.
-
This seems to be an issue with your custom texture pack not proving the proper colors for grass.
The texture size should be 256x256 which makes it 65535 for that array, so ya, texture pack issue it seems.
Or something with optifine.
-
How about.. setTextureFile... no.. thats to freakin obvious.
-
Look at IArrowNock/LooseHandlers
-
Alright just to shut up people
You cant
I want to add a hook for this but its very low on my priorities list right now.
People who are saying reflection, please stop being a dick and only say reflection when you are right.
-
Have you even freakin looked at the class?
You already can.
-
Don't use MCPatcher to install mods esp if you're installing the yogsbox it comes with a installer...
-
So.... you're creating instances of items.. that are vanilla classes, never telling them you want them to use a custom texture.. and expecting them to use a custom texture...
Also, you're edting base classes.. awesome...
-
Update your JDK.
-
Post a log of recompile
-
-
Actually no, it has something to do with Forestry, its trying to access something called stump.
There isnt anything named that in Minecraft. Bug or install problem with Forestry.
-
MLMP has been unneeded and incompatible for quite some time.
-
Do a search for Colorizer, even when you disable everything that crap gets injected.
And please don't even assume you know anything about how MCPatcher works or bytecode injection, else you wouldn't be so high and mighty.
Bytecode injection is good for SMALL things, I actually have a project for 1.3 that i've been working on that will massivly simplify things. However, its is not a valid solution for large scale things like Optifine or Forge.
Yes the functionality of 'put all mods here and click button poof installed' is nice.
And can be done quite easily with a lot of other tools.
As for the whole issue of communicating with TexturePack authors, thats Mojangs/Optifines/MCPatchers jobs not forge.
I see no legitimate reason to take over there functionality. From every usage case I have found Optifine works perfectly fine. Does everything a TexturePack author needs, and hes open to speaking with people about improvements. Hes not the fastest person on the block but he gets the job done.
As I said, the FML HD texture modifications were BUG FIXES. Nothing more.
They fixed the BUGS in Vanilla MC that made the game CRASH and massive visual artifacts while playing.
We never intended to be the one stop shop for all texture related needs, as I said it already exists in Optifine, there is no reason for us to do it.
So I ask this, give me a VALID reason that we should absorb MCPatcher.
Bytecode injection is not a valid reason.
Texturepack authors are not valid reason, they already have there solutions.
The ONLY valid reason is for simpler installation for the end user, and there are discussions going on directly for that that have nothing to do with MCPatcher.
-
Thread locked cuz you're a moron.
-
Of optifine, any of the C series should work, but try the latest C.
-
Reinstall optifine and make sure you're using a compatible version
minecraft server crashes with forge 3.3.8.164
in Support & Bug Reports
Posted
.. it sould never try unless you're running it from the windows dir, how are you running it?