daifei4321

If you have 2 mods, and mod2 depends on mod1, maybe you can do this: While loading mod2, checking for mod1, as you did now. If mod1 does not exist, set a trigger like "interface Mod1Requester". While loading mod1, checking for mod2. If mod2 exists already, checking for certain trigger. If the trigger exists, call it like "((Mod1Requester) mod2).hereComesMod1()".

Hello. If these changes are hard to perform, can someone give me some hints?

In fact, I don't know why this limitation exists: (still in 1.2.5) At client: net.minecraft.src.ChatAllowedCharacters defined allowed chars.(1) net.minecraft.src.GuiEditSign allow only allowed characters.(2) net.minecraft.src.GuiScreen.handleKeyboardInput handle only 1 input character.(3) At server: net.minecraft.src.NetServerHandler handleChat forces only allowed chars in chatting.(4) handleUpdateSign replaces all not-allowed chars.(5) Is it because some character are used for controlling somewhere? Someone made changes and removed these 5 limitations, and it works well so far. (for point3, added processing code) I usually use Chinese, and Java supports UTF8 by default, so I want to remove these limitation beside using forge. At client side, no file confliction. However, at server side, mm.class (NetServerHandler.java) collide. I compiled a proper NetServerHandler for my friends this time to include both chinese_support_mod and forge. Is it possible that these limitation be removed directly while injection forge? What does chinese_support_mod do: (1) added definition of gbk characters (2) allow also gbk defined before (3) if (c > 128 && org.lwjgl.Sys.getVersion().compareTo("2.8.0") < 0){Keyboard.next();char c2 = Keyboard.getEventCharacter();c = (new String(new byte[] {(byte)c, (byte)c2}, java.nio.charset.Charset.defaultCharset().toString().toLowerCase())).toCharArray()[0];} (4) removed such code (5) removed such code Is it possible just remove this whole 'AllowedCharacters' thing?