Kalbintion

780 isnt the id number being used, 780 is part of the authors name (apparently its jammy780) - the ID being used is 4094. The block from the jammys furniture mod is "jfm_WoodBlocksTwo" - whatever the hell "WoodBlocksTwo" means is beyond me. As for the Mystcraft block, its the "Lectern".

Post this issue on the tracker, link in signature below as well as read the guidelines on posting on the tracker.

Did you try ";"

By installing the mod. And yes, assuming theres a version compatible with the forge version used in that pack.

It does belong in the platform pagoda though since it is now a custom modpack. So, still reportable.

Not to mention posting in the wrong location. Adding mods to a pack makes it a custom modpack, therefore the issue belongs in the platform pagoda instead.

Custom modpack questions would be best posted in the Platform Pagoda.

The only reason mystcraft errored is because it was being loaded after the furniture mod being added was loaded first. The ID conflict still is there, regardless of what you may think. The solution is what Roversword said originally - though you can edit either the mystcraft config or the furniture mod config and change the block id of the conflicting block to an id that isnt being used.

Lets see the repercussions of adding microblocks and carpenter blocks to be sealable: All blocks now become sealable through the use of carpenter blocks. You can now have holes in your base that completely void the use of air locks because microblocks now count as sealable Edit: If you missed the point. No, bad idea. It's overpowered and defeats the point of having sealable and non-sealable blocks. If you want to do it locally, fine, but I would never have this be a suggestion to anyone.

Run the game, click multiplayer, click "Add Server", give them a name, and put in the IP and PORT they provide to the server. Click "Done" ("Accept", or whatever the finished button is called, dont remember) then it should appear on your multiplayer list. You can then either double click the server to join it, or click it then click "Join Server" Another thing to look out for: Ensure you're running the same version of the modpack as the server is, otherwise you will be told of microblocks missing, or other ID type issues that arise from mismatched versions. You generally should be able to find what version of the modpack the server is running in their respective server thread.

Not always true. Worldgen stuff such as biomes can cause crashes, however trees and the like wont cause crashes, theyll simply vanish (with a warning about id mismatches or missing prior to loading the world) and turn into air.

In the future, issues belong on the tracker. Link at top of page.

Platform Pagoda is where you should go. They're the place that does the whole custom modpack help, and installing Cauldron (formerly MCPC+) is making the pack custom.

Issues belong on the tracker. Link at top of page.

Issues belong on the tracker. If you want to save yourself the trouble of duplicating a known issue, read the common issues and solutions thread in this section, or just browse any number of these tracker reports: http://forums.technicpack.net/tracker/issue-2010- http://forums.technicpack.net/tracker/issue-2821- http://forums.technicpack.net/tracker/issue-2865- http://forums.technicpack.net/tracker/issue-2883- http://forums.technicpack.net/tracker/issue-2931- http://forums.technicpack.net/tracker/issue-2937- http://forums.technicpack.net/tracker/issue-2955- http://forums.technicpack.net/tracker/issue-2975- http://forums.technicpack.net/tracker/issue-2981- http://forums.technicpack.net/tracker/issue-3007- http://forums.technicpack.net/tracker/issue-3077- http://forums.technicpack.net/tracker/issue-3133- http://forums.technicpack.net/tracker/issue-3150- http://forums.technicpack.net/tracker/issue-3187- http://forums.technicpack.net/tracker/issue-3196- http://forums.technicpack.net/tracker/issue-3208- http://forums.technicpack.net/tracker/issue-3212- http://forums.technicpack.net/tracker/issue-3239- http://forums.technicpack.net/tracker/issue-3254- http://forums.technicpack.net/tracker/issue-3263- http://forums.technicpack.net/tracker/issue-3283- http://forums.technicpack.net/tracker/issue-3290- http://forums.technicpack.net/tracker/issue-2880- http://forums.technicpack.net/tracker/issue-3186- http://forums.technicpack.net/tracker/issue-3249- http://forums.technicpack.net/tracker/issue-3326- http://forums.technicpack.net/tracker/issue-3353- http://forums.technicpack.net/tracker/issue-3422-

Hm, I've never played this modpack before but figured that generator option wouldve been around for a long time, that option is in the natura config for attack of the b-team. Let me get the modpack and take a look at the config for natura and icbm to see if theres an alternative, as if the option wasnt already in the config, it wont be considered at all since it wasnt implemented. Presently downloading the modpack (its verifying atm) so give me a moment to edit this post with what i find. Edit: Alright, here's what I found I:"Cloud Spawn Height"= I:"Cloud Spawn Range"= I:"Cloud Spawn Rarity"= Those three values are in the nature.txt file for this modpack, messing with those, ive been getting crashes or nothing i can figure out for the rarity value (set to 0, set to 100, seems to still spawn them about the same) so im not sure what the rarity value does. These could be messed with for the height (set to 255, then set range to 1, setting range to 0 caused a crash, this would be at the world build limit, less likely to hit but still possible) The other option is messing with the cloud ID, but this could cause you to be unable to join servers, so i didnt want to go this route originally. The height, range, and rarity values though are only for local worlds so they wont interfere with joining on servers. If you wanted to go with the ID route, setting it to empty or to 0 could remove them from spawning at all (since they wont be added to the block list) but this can cause its own issues, and not with joining servers itself.

If its frozen, not only why is it on the launcher, but why is there a tracker section for it?

Issues belong on the tracker, link at top of page.

Issues belong on the tracker. Link at top of the page.

Issues belong on the tracker, link at top of page.

Post the issue on the tracker, link at top of page.

Issues belong on the tracker, link at top of page.

Issues belong on the tracker. Link at top of page. Also, don't spill your log.

@Fancyboss - dont use the vanilla jar, use the BigDig.jar or the launch.bat associated with the modpack, and you wont have this issue. To everyone else: they dont have time nor is it their responsibility to respond to every single post on these forums, they do what they can. Edit: Oh, @Fancyboss - that list tidbit of the post i missed originally: You dont extract the jar, you execute it. If you have issues using it or the launch file with the pack, post on the tracker then, link at top of page.