Jump to content

LexManos

Forge Code God
  • Posts

    9264
  • Joined

  • Last visited

  • Days Won

    66

Posts posted by LexManos

  1. 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.

  2. 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.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.