[1.6.4] HappyDiggers AMP - Updated - Now with 98% more Awesome!
- Thread starter InsaneJ
- Start date
-
The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord
You say fix, but I think you mean the other thing 
I appreciate that you guys are modding our mod pack. Seriously, go for it. Just so everyone knows, you don't need our permission to do anything since the mods don't belong to us. All mods included in AMP can be used for private packs in any way you like. Public packs are a completely different matter though.
Please keep in mind that it took us 15 test versions of AMP before we considered it to be stable enough to launch the Minecraft 1.6.4 version of the pack. And after that many versions came out that solved many issues. Bugs and glitches are to be expected when you add stuff to any mod pack. You need to figure out what's going wrong so you can send a proper bug report to the right mod author so that he/she can fix the problem. That is the only way mods can get fixed, you need to submit good bug reports to the right people.
I appreciate that you guys are modding our mod pack. Seriously, go for it. Just so everyone knows, you don't need our permission to do anything since the mods don't belong to us. All mods included in AMP can be used for private packs in any way you like. Public packs are a completely different matter though.
Please keep in mind that it took us 15 test versions of AMP before we considered it to be stable enough to launch the Minecraft 1.6.4 version of the pack. And after that many versions came out that solved many issues. Bugs and glitches are to be expected when you add stuff to any mod pack. You need to figure out what's going wrong so you can send a proper bug report to the right mod author so that he/she can fix the problem. That is the only way mods can get fixed, you need to submit good bug reports to the right people.
You say fix, but I think you mean the other thing
I appreciate that you guys are modding our mod pack. Seriously, go for it. Just so everyone knows, you don't need our permission to do anything since the mods don't belong to us. All mods included in AMP can be used for private packs in any way you like. Public packs are a completely different matter though.
Please keep in mind that it took us 15 test versions of AMP before we considered it to be stable enough to launch the Minecraft 1.6.4 version of the pack. And after that many versions came out that solved many issues. Bugs and glitches are to be expected when you add stuff to any mod pack. You need to figure out what's going wrong so you can send a proper bug report to the right mod author so that he/she can fix the problem. That is the only way mods can get fixed, you need to submit good bug reports to the right people.
is there any way to repair bugged map? map generated by alternate map generator from HPAMP has big empty inaccessible area with no blocks. It looks weird.
Remove the chunks using an editor like MCEdit. Then when you restart the game those chunks should be regenerated. Just take care to use the same world generator and seed or else you'll get weird new chunks that don't fit the landscape.
Or if you are running a server you could simply use WorldEdit to remove/regen the chunks.
Or if you are running a server you could simply use WorldEdit to remove/regen the chunks.
Well, im not sure what was wrong, but when i loaded map into mcedit, bugged area was gone. "WTF?, lets try it in minecraft", was my first though, and voila! everything is working. i didn\t even save map in mcedit... Maybe it was a bug in game...
Are you using Optifine? Because that is known to cause chunks to magically disappear on heavily modded Minecraft instances. That is also why we don't recommend using Optifine. It breaks more then the performance gain is worth on a lot of mod packs, and I don't mean just chunks disappearing. It's known to cause a lot off other glitches as well.
Anway, glad the problem is solved now
Anway, glad the problem is solved now
AMP has been updated to v2.5.1 with the following changelog:
v2.5.1
-Reduced spawn rates and difficulty for Lycanites Mobs.
-Updated DragonAPI to 1.6 V21
-Updated EnderForest to 1.6 V21
-Updated Galacticraft to 2.0.12.1023
-Updated Galacticraft to 1.6.4-2.0.12.1023
-Updated LycanitesMobs to 1.5.0b
-Updated MicdoodleCore to 2.0.12.1023
-Updated ReactorCraft to 1.6 V21
-Updated RotaryCraft to 1.6 V21b
v2.5.0
-Added Lycanites Mobs
-Added Roguelike Dungeons
-Changed Damage Indicators back to 2.9.2.3. Merry Christmas!
-Disabled Tornados grabbing blocks. Players and mobs still get lifted.
-Updated BigReactors to 0.3.2A
-Updated DartCraft to Beta 0.2.18
-Updated DragonAPI to 1.6 V20f
-Updated EnderForest to 1.6 V20
-Updated EnderIO to 1.0.1.353
-Updated Galacticraft to 2.0.12.1020
-Updated Galacticraft-Planets to 2.0.12.1020
-Updated Growthcraft to 2.0.6
-Updated Hardcore Ender Expansion to 1.5a
-Updated Hats to 2.1.5
-Updated LogisticsPipes to 0.7.4.dev.157
-Updated Mekanism to 6.1.0.38
-Updated MekanismGenerators to 6.1.0.38
-Updated MekanismTools to 6.1.0.38
-Updated MicdoodleCore to 2.0.12.1020
-Updated MobiusCore to 1.2.0
-Updated OpenPeripheralCoreto 0.3.3-snapshot-118
-Updated OpenPeripheralAddons to 0.1.3-snapshot-95
-Updated OpenModsLib to 0.4-snapshot-184
-Updated OpenBlocks to 1.2.7-snapshot-364
-Updated Opis to 1.2.1
-Updated ReactorCraft to 1.6 V20f
-Updated RotaryCraft to 1.6 V20f
-Updated Tinkers Construct to 1.5.5.2
-Updated Tinkers Mechworks to 0.1.6
-Updated Tropicraft to 5.1.7
-Updated Waila to 1.5.2
v2.5.1
-Reduced spawn rates and difficulty for Lycanites Mobs.
-Updated DragonAPI to 1.6 V21
-Updated EnderForest to 1.6 V21
-Updated Galacticraft to 2.0.12.1023
-Updated Galacticraft to 1.6.4-2.0.12.1023
-Updated LycanitesMobs to 1.5.0b
-Updated MicdoodleCore to 2.0.12.1023
-Updated ReactorCraft to 1.6 V21
-Updated RotaryCraft to 1.6 V21b
v2.5.0
-Added Lycanites Mobs
-Added Roguelike Dungeons
-Changed Damage Indicators back to 2.9.2.3. Merry Christmas!
-Disabled Tornados grabbing blocks. Players and mobs still get lifted.
-Updated BigReactors to 0.3.2A
-Updated DartCraft to Beta 0.2.18
-Updated DragonAPI to 1.6 V20f
-Updated EnderForest to 1.6 V20
-Updated EnderIO to 1.0.1.353
-Updated Galacticraft to 2.0.12.1020
-Updated Galacticraft-Planets to 2.0.12.1020
-Updated Growthcraft to 2.0.6
-Updated Hardcore Ender Expansion to 1.5a
-Updated Hats to 2.1.5
-Updated LogisticsPipes to 0.7.4.dev.157
-Updated Mekanism to 6.1.0.38
-Updated MekanismGenerators to 6.1.0.38
-Updated MekanismTools to 6.1.0.38
-Updated MicdoodleCore to 2.0.12.1020
-Updated MobiusCore to 1.2.0
-Updated OpenPeripheralCoreto 0.3.3-snapshot-118
-Updated OpenPeripheralAddons to 0.1.3-snapshot-95
-Updated OpenModsLib to 0.4-snapshot-184
-Updated OpenBlocks to 1.2.7-snapshot-364
-Updated Opis to 1.2.1
-Updated ReactorCraft to 1.6 V20f
-Updated RotaryCraft to 1.6 V20f
-Updated Tinkers Construct to 1.5.5.2
-Updated Tinkers Mechworks to 0.1.6
-Updated Tropicraft to 5.1.7
-Updated Waila to 1.5.2
Short answers
Yes.
No.
Change B:Storm_Tornado_grabBlocks in config\WeatherMod\Storm&Tornado.cfg
As a rule we try to prevent any major changes in world gen that break backward compatibility. The only major break we've had so far was when going from Minecraft 1.5.2 to Minecraft 1.6.4. But even then worlds could be carried over if you really wanted to.
Yes.
No.
Change B:Storm_Tornado_grabBlocks in config\WeatherMod\Storm&Tornado.cfg
As a rule we try to prevent any major changes in world gen that break backward compatibility. The only major break we've had so far was when going from Minecraft 1.5.2 to Minecraft 1.6.4. But even then worlds could be carried over if you really wanted to.
I decided to generate map again from the same seed and its awesome. There is only one new tower near spawn... 2 ravines+abandoned mines and 2 solo ravines nearby. Did you change spawn rate of these things?Short answers
Yes.
No.
Change B:Storm_Tornado_grabBlocks in config\WeatherMod\Storm&Tornado.cfg
As a rule we try to prevent any major changes in world gen that break backward compatibility. The only major break we've had so far was when going from Minecraft 1.5.2 to Minecraft 1.6.4. But even then worlds could be carried over if you really wanted to.
Ok, last question here. When ftb launcher is loading minecraft there are many log lines of red text. Many missing textures, block types, etc. Is it normal, or should I be worried?
Feel free to ask as many questions as you like, I don't mind
It's nothing to worry about. Most of the stuff is just sloppy coding by several mod devs but nothing serious enough to warrant an immediate fix by them. Mostly they'll get around to fixing those issues eventually when there's nothing more important that needs fixing first.
To give you an idea. If it doesn't crash the client, and it doesn't break the game: it's a low priority. Which is what most of those warnings are.
As mod development and AMP progress you'll see that most of those messages will slowly disappear over time
It's nothing to worry about. Most of the stuff is just sloppy coding by several mod devs but nothing serious enough to warrant an immediate fix by them. Mostly they'll get around to fixing those issues eventually when there's nothing more important that needs fixing first.
To give you an idea. If it doesn't crash the client, and it doesn't break the game: it's a low priority. Which is what most of those warnings are.
As mod development and AMP progress you'll see that most of those messages will slowly disappear over time
Hey InsaneJ,
I really enjoy your videos and me and my friends are trying to use the newest available server for HappyDIggersAMP. Do you have any recommendations on what the server needs to be running in terms of OS, processors, obviously a good amount of ram. We tried several configurations with it and we are getting the same crash when another player joins the server.
Here is our crash log, we are hoping to get this to work.This log was taken from a Debian VM running 8 cores and 8 Gb of RAM, so we were hoping it would be enough. Again we really like this modpack in single player. Any help is appreciated in advance.
http://pastebin.com/YsDLBEwA
Regards,
Gustaberg
I really enjoy your videos and me and my friends are trying to use the newest available server for HappyDIggersAMP. Do you have any recommendations on what the server needs to be running in terms of OS, processors, obviously a good amount of ram. We tried several configurations with it and we are getting the same crash when another player joins the server.
Here is our crash log, we are hoping to get this to work.This log was taken from a Debian VM running 8 cores and 8 Gb of RAM, so we were hoping it would be enough. Again we really like this modpack in single player. Any help is appreciated in advance.
http://pastebin.com/YsDLBEwA
Regards,
Gustaberg
Glad you like them
The crash report doesn't make it clear to me why your server is crashing. You could try updating MCPC+ to the latest build. You can download it here: http://ci.md-5.net/job/MCPC-Plus-164/
The next version of AMP will have the latest MCPC+ in it. MD5 has made quite a few bug fixes since the last version, maybe it'll solve your problem. In case it doesn't, i'll be submitting a new version of AMP to the FTB mod pack team tomorrow which should become available on the FTB client on friday/saturday-ish.
As for your server specs. 8GB is more then enough to run an AMP server. In fact the HappyDiggers AMP server we use to test new builds of the pack uses 7GB currently. WIth a hand full of players that's plenty. You will run out of CPU capacity long before you run out of RAM. Which brings me to the next point. 8 cores may sound impressive, but since Minecraft's main thread is still very much a single threaded affair, you are better off with higher clock speed then with more cores. Of course a lot of the stuff in AMP is off loaded from the main thread, but the main thread is till the largest bottleneck by far.
To give you an idea. The HappyDiggers AMP server runs on a Core i7 3770K @4GHz. and it does around 30~40ms per tick with 8 players on. That is with my current base you can see in my latest YouTube videos. So that's quite a lot of stuff going on all at once and performance is good. However you can really kill a server by using large amount of cable to transport energy of any kind. So IC2 wires, energy conduits, Ender IO cable, Mekanism Universal cable, they all cause a lot of lag if you use long cables or large cable networks. Wireless energy transfer is definitely the way to go once you reach a certain stage of development. I've replaced all the cable in my base with IDSUs, it's expensive but it's well worth it.
A good way to monitor server performance is by using Opis which is included in AMP. Only players who are OP on a server can use the /opis command which will open up a small window outside of Minecraft which will display a ton of useful information about how your server is doing so check it out once you get the server up and running.
The crash report doesn't make it clear to me why your server is crashing. You could try updating MCPC+ to the latest build. You can download it here: http://ci.md-5.net/job/MCPC-Plus-164/
The next version of AMP will have the latest MCPC+ in it. MD5 has made quite a few bug fixes since the last version, maybe it'll solve your problem. In case it doesn't, i'll be submitting a new version of AMP to the FTB mod pack team tomorrow which should become available on the FTB client on friday/saturday-ish.
As for your server specs. 8GB is more then enough to run an AMP server. In fact the HappyDiggers AMP server we use to test new builds of the pack uses 7GB currently. WIth a hand full of players that's plenty. You will run out of CPU capacity long before you run out of RAM. Which brings me to the next point. 8 cores may sound impressive, but since Minecraft's main thread is still very much a single threaded affair, you are better off with higher clock speed then with more cores. Of course a lot of the stuff in AMP is off loaded from the main thread, but the main thread is till the largest bottleneck by far.
To give you an idea. The HappyDiggers AMP server runs on a Core i7 3770K @4GHz. and it does around 30~40ms per tick with 8 players on. That is with my current base you can see in my latest YouTube videos. So that's quite a lot of stuff going on all at once and performance is good. However you can really kill a server by using large amount of cable to transport energy of any kind. So IC2 wires, energy conduits, Ender IO cable, Mekanism Universal cable, they all cause a lot of lag if you use long cables or large cable networks. Wireless energy transfer is definitely the way to go once you reach a certain stage of development. I've replaced all the cable in my base with IDSUs, it's expensive but it's well worth it.
A good way to monitor server performance is by using Opis which is included in AMP. Only players who are OP on a server can use the /opis command which will open up a small window outside of Minecraft which will display a ton of useful information about how your server is doing so check it out once you get the server up and running.
Im a little deeper into HDAMP (literally too And i found few problems.
1.Treetap is useless. Rubber trees are not generating from ic2...
2. Some plants from Pam's Harvestcraft base are missing textures/animations/names
3. You should add mod that makes new mobs thaumaturgy compatible
4. Some nei recipes are not working, some are unaccessible.
Is there any video with HDAMP survival? There are so many mods in pack that it's really hard to start develop high tech. basiclly Macerator. Macerator need battery. battery need cable and tin something. Cable need rubber... I found many videos "how to build macerator", on you tube, but all of them are different than version used in pack. Seriously, you need video that show how to surviwe up to first generator/macerator etc...
And i found few problems.1.Treetap is useless. Rubber trees are not generating from ic2...
2. Some plants from Pam's Harvestcraft base are missing textures/animations/names
3. You should add mod that makes new mobs thaumaturgy compatible
4. Some nei recipes are not working, some are unaccessible.
Is there any video with HDAMP survival? There are so many mods in pack that it's really hard to start develop high tech. basiclly Macerator. Macerator need battery. battery need cable and tin something. Cable need rubber... I found many videos "how to build macerator", on you tube, but all of them are different than version used in pack. Seriously, you need video that show how to surviwe up to first generator/macerator etc...
Moved to a Actual I7 machine and we are still getting this crash when someone joins, other then that everything is running fine. I updated MCPC+, or at least i think i did, and we tried disabling some mods to see if that would work. No DICE. I have attached the crash reports this time maybe you guys can help us out, it really does not make sense. I am running this on a physical server i7 core extreme, 8 gigs of ram atc, running latest ubuntu.
Really want to play this modpack, and it's hard to find info about this particular crash.
Cheers,
1. This is by design. You should use the rubber trees from Minefactory Reloaded. The IC2 and MFR rubber is interchangeable.Im a little deeper into HDAMP (literally too
1.Treetap is useless. Rubber trees are not generating from ic2...
2. Some plants from Pam's Harvestcraft base are missing textures/animations/names
3. You should add mod that makes new mobs thaumaturgy compatible
4. Some nei recipes are not working, some are unaccessible.
Is there any video with HDAMP survival? There are so many mods in pack that it's really hard to start develop high tech. basiclly Macerator. Macerator need battery. battery need cable and tin something. Cable need rubber... I found many videos "how to build macerator", on you tube, but all of them are different than version used in pack. Seriously, you need video that show how to surviwe up to first generator/macerator etc...
2. Nothing I can do about that. Pam is going through some rough times and as a result hasn't been able to spend much time modding fixing minor bugs.
3. I'm not exactly sure what you're getting at here. Feel free to make a suggestion and help me understand what it is exactly that you want to do
4. NEI has never been 100% accurate. Usually the fault lies with mods other then NEI. If you can tell me which recipes are missing for you, then perhaps we can add them through different means so they show up in NEI. We did this for a couple of IC2 and GregTech recipes to help players not get stuck in the tech progress tree.
I'm getting a second opinion on those crash reports and will report back as soon as possible. Would you mind posting a ForgeModLoader-server-0.log of when the crash occurs? You should be able to post it on http://paste2.org if it's too large to attach to the forum.
For the mean time it looks like you are using MCPC+ build 250. You chould try switching to the latest build, currently 259. Although that's not likely to be the cause of your crashes, it also can't hurt to update
http://ci.md-5.net/job/MCPC-Plus-164/
Also you are using OpenJDK. On the HappyDiggers server we use Oracle Java. Mainly because it's faster. It shouldn't matter, but you might try switching to Oracle Java and see if that helps.
Do the crashes occur with every player joining, or just a (few) specific ones? Could it be location specific? Did you try renaming/deleting their player.dat files?
Last edited:
Would you mind posting a ForgeModLoader-server-0.log of when the crash occurs? You should be able to post it on http://paste2.org if it's too large to attach to the forum.
For the mean time it looks like you are using MCPC+ build 250. You chould try switching to the latest build, currently 259. Although that's not likely to be the cause of your crashes, it also can't hurt to update
http://ci.md-5.net/job/MCPC-Plus-164/
Also you are using OpenJDK. On the HappyDiggers server we use Oracle Java. Mainly because it's faster. It shouldn't matter, but you might try switching to Oracle Java and see if that helps.
Do the crashes occur with every player joining, or just a (few) specific ones? Could it be location specific? Did you try renaming/deleting their player.dat files?
Hey InsaneJ,
Thanks for you prompt feedback. We are using OpenJDK, and we did have that in common in all tests, although I think more people might have experienced this issue if it was so easy to reproduce. The crashes happen immediately when any player joins the server. We tried to move location, re-spawn the world and delete player data. I will post the ForgeModLoader-server-0.log as soon as I have access to it.
In case you want to install Oracle's version of java on Debian:
http://www.webupd8.org/2012/06/how-to-install-oracle-java-7-in-debian.html
http://www.webupd8.org/2012/06/how-to-install-oracle-java-7-in-debian.html