Are you sure its a bug? I'm not sure but I thought that the obsidian platform had to be reset each time to stop you from spawning in the void by accident? I'm not sure though
I'm pretty sure it isn't a bug, but since people don't know any better they assume it is.
Since it's a new pc have you updated your graphics drivers to the latest versions? Also you mentioned playing on snapshot versions, in the video settings make sure enable VBOs is set to true.
If it is a bug please link to the bug report from the Minecraft bug list, because I cannot find a bug report on there and am nearly positive this is intended behavior.
This is not a bug, anything placed on the 5x5 obsidian square is deleted when someone enters the end, this is because in multiplayer people could fill the entrance area and cause anyone who enters the end to suffocate and die. If you want to place something in the end make sure its not on the 5x5 area, just outside of it should be safe.
Looks really cool, if you need any help with just general programming, I'd love to lend a hand, I'm fairly experienced with Java and Forge/Minecraft Mod development.
Very nice program, I would like to note though, that your build.sh doesn't seem to copy your image icons into the jar, I had to put them in manually (It wouldn't launch without them, null pointer exception), other then that it works very well and is very useful!
This might be more difficult than I originally thought, it would seem (and it makes sense) that NEI is telling the server to update the client with the items (which again is correct), but because my GUI only exists on the client it will be hard to get the inventory update.
Yeah I mention how to in my previous post, also that second crash would appear to be a separate issue, looks like it might originate with the journeymap mod, but it could come from elsewhere.
odd since i am letting it use 8gbs of ram and my computer has 32 gbs ram total :S i will see if it some how caps it with F3.
also my launcher has this -Xmx8G if that helps at all. also i will try finding a crash log.
That's the amount of ram allocated to the JVM, not the PermGen, it's completely seperate from that. Could you tell me which launcher you're using? There's some information here that i found on another forum post at the bottom of the page about permgen.
If there's a PermGen error anywhere in the log than you can be 99,99% sure any other errors were caused by the game running out of PermGen. Since it was unable to load all the mods' compiled classes into memory.
Not the other way around. A mod would have to be royally messed up to cause a PermGen error as a side-effect of some other programming bug.
Alright, I'll admit when I'm wrong, I'd misread what you wrote previously and assumed it was a regular out of memory issue, however ops question remains unanswered, basically you need to increase the amount of memory being allocated to permgen via your launcher. I believe it defaults to 64m, I don't have the launcher in front of me, but in the default launcher I believe if you open your profile settings there is a place for JVM settings near the bottom, if there isn't anything that looks like -XX:MaxPermSize=64m add it and change the 64 to 128 or more.
Keep in mind I'm not looking at the launcher and this is all off memory, so it might be different.
Look higher in the stack trace, there's an index out of bounds exception that caused the out of memory error. On mobile so hard to quote.
On another note that index out of bounds exception could have been caused by something else higher up, so without the entire log we can't know for sure what the actual cause is.
Okay, I understand the bug now, and it shouldn't be too hard to fix either, basically I just need to update the inventory slots, also if you exit to the main menu of the recipes and go back in it should update
0
I'm pretty sure it isn't a bug, but since people don't know any better they assume it is.
0
0
0
If it is a bug please link to the bug report from the Minecraft bug list, because I cannot find a bug report on there and am nearly positive this is intended behavior.
2
0
0
0
0
0
That's the amount of ram allocated to the JVM, not the PermGen, it's completely seperate from that. Could you tell me which launcher you're using? There's some information here that i found on another forum post at the bottom of the page about permgen.
0
Alright, I'll admit when I'm wrong, I'd misread what you wrote previously and assumed it was a regular out of memory issue, however ops question remains unanswered, basically you need to increase the amount of memory being allocated to permgen via your launcher. I believe it defaults to 64m, I don't have the launcher in front of me, but in the default launcher I believe if you open your profile settings there is a place for JVM settings near the bottom, if there isn't anything that looks like -XX:MaxPermSize=64m add it and change the 64 to 128 or more.
Keep in mind I'm not looking at the launcher and this is all off memory, so it might be different.
0
Look higher in the stack trace, there's an index out of bounds exception that caused the out of memory error. On mobile so hard to quote.
On another note that index out of bounds exception could have been caused by something else higher up, so without the entire log we can't know for sure what the actual cause is.
0
0
0
sang if you mean this post, I can't watch that video it's private.