When I first saw this, Loved it. It reminded me of the one that is used in YogCraft, but when I first saw this, I haven't played that in ages. I have been playing YogCraft lately and I am realizing that this one is way better!
For some reason with the mod installed i cant join 1.6.4 Servers :\ says i dont have the version but when I remove the mod i can play on them again.
Version: minecraftforge-installer-1.6.4-9.11.1.916 chained with Liteloader 1.6.4
Yes, I did notice that happening with one of my servers when I was testing the update. I thought it might have been related just to the one server, so it's good to know that it's a broader issue.
I'll look into it, but as a temporary work-around, I've found that you can still connect to the servers by clicking "Direct Connect" and entering the IP manually.
Actually, just as I'm typing this, I remembered that this happened last time I bumped the MC version, and it has to do with Novamenu still identifying itself to servers as being on MC 1.6.2 (even though it isn't). So this will probably be fixed later today.
No longer says outdated on the server menu but when you I click the server still says: Outdated client!
Good catch. Try redownloading v1.1.4, it should work now.
For anyone who's curious, here's the technical explanation: Minecraft's netcode doesn't use human-readable versions (e.g. "1.6.4") internally. Instead, it uses numbers to indicate the version and its placement relative to other versions. For instance, 1.6.2 was represented by the number 72, but 1.6.4 was represented by the number 78. Since a portion of the server-connectivity code in vanilla Minecraft is private to the vanilla GUIs that are responsible for spawning the connections, when I replace the GUIs for Novamenu, I also have to replace those parts of the netcode with my own versions (which don't automatically update with Mojang's changes). These parts of the code are what are responsible for sending those numerical codes back and forth between the server and client. The problem was just one line that I forgot to change buried inside a thread, which sent a packet to the server telling it that the client was "version 72". The server interprets that as meaning 1.6.2, concludes (incorrectly) that the client is out of date, and disconnects you.
I changed "72" to "78" to fix that. Just another example of how a single character can mess up your code badly.
It would be REALLY great if you could add a customizable direct server connect button.
If a play one server a lot and I don't wanna go to multilayer -> the server each time,
make a button you can setto a server and rename and when you click it you connect directly...
Anyway GREAT MOD!!!!
Rollback Post to RevisionRollBack
Mute Pack Generator - the online tool that lets you mute specific sounds in vanilla.
It generates a custom resource pack from the sounds you select to mute,
The end to the annoying villager, portal and more sounds!
It would be REALLY great if you could add a customizable direct server connect button.
If a play one server a lot and I don't wanna go to multilayer -> the server each time,
make a button you can setto a server and rename and when you click it you connect directly...
Anyway GREAT MOD!!!!
Interesting idea, that sounds like something that might be worth adding. I'll keep that one in mind for the future :-)
novamenu is a coremod for Minecraft Forge. You need to have an installation of Minecraft modded with Forge for Minecraft 1.6.4 before you can install Novamenu. I may look into making Novamenu not dependent on Forge in the future, but for now Forge is a requirement.
Please make sure that your modded Minecraft works before attempting to install Novamenu. I don't want you coming here to report errors caused by a broken Forge installation.
If you have Forge installed and working, download Novamenu here. (version 1.1.4 for MC 1.6.4)
Drop the .jar file into the "mods" folder inside your ".minecraft" folder.
Lol, what folder do i put it in? the core mods, or the mods... i'm gonna try the mods
Rollback Post to RevisionRollBack
I could put something clever here... but i decided not to...
The Meaning of Life, the Universe, and Everything.
Join Date:
10/16/2012
Posts:
45
Minecraft:
AuraPerson
Member Details
I installed the mod correctly, but when I open Minecraft, the background and the "Minecraft" logo are blank. It's the same error as glman99. (Quote Below)
So, I dropped the jar into my coremods folder, but when launched, the GUI appeared on a white background, and when looking through my files, it seems that it never created a folder in the mods folder with the images in it. Any idea on how to fix it?
It already is.
Just change 'true' to 'false' in the options section in the config file and you'll be golden
And i dont even play minecraft anymore.
Version: minecraftforge-installer-1.6.4-9.11.1.916 chained with Liteloader 1.6.4
Yes, I did notice that happening with one of my servers when I was testing the update. I thought it might have been related just to the one server, so it's good to know that it's a broader issue.
I'll look into it, but as a temporary work-around, I've found that you can still connect to the servers by clicking "Direct Connect" and entering the IP manually.
Actually, just as I'm typing this, I remembered that this happened last time I bumped the MC version, and it has to do with Novamenu still identifying itself to servers as being on MC 1.6.2 (even though it isn't). So this will probably be fixed later today.
Good catch. Try redownloading v1.1.4, it should work now.
For anyone who's curious, here's the technical explanation: Minecraft's netcode doesn't use human-readable versions (e.g. "1.6.4") internally. Instead, it uses numbers to indicate the version and its placement relative to other versions. For instance, 1.6.2 was represented by the number 72, but 1.6.4 was represented by the number 78. Since a portion of the server-connectivity code in vanilla Minecraft is private to the vanilla GUIs that are responsible for spawning the connections, when I replace the GUIs for Novamenu, I also have to replace those parts of the netcode with my own versions (which don't automatically update with Mojang's changes). These parts of the code are what are responsible for sending those numerical codes back and forth between the server and client. The problem was just one line that I forgot to change buried inside a thread, which sent a packet to the server telling it that the client was "version 72". The server interprets that as meaning 1.6.2, concludes (incorrectly) that the client is out of date, and disconnects you.
I changed "72" to "78" to fix that. Just another example of how a single character can mess up your code badly.
It would be REALLY great if you could add a customizable direct server connect button.
If a play one server a lot and I don't wanna go to multilayer -> the server each time,
make a button you can setto a server and rename and when you click it you connect directly...
Anyway GREAT MOD!!!!
Interesting idea, that sounds like something that might be worth adding. I'll keep that one in mind for the future :-)
And i dont even play minecraft anymore.
Lol, what folder do i put it in? the core mods, or the mods... i'm gonna try the mods
I could put something clever here... but i decided not to...