PSA: Monster 1.0.6 and 1.0.7 Hotfix

[Eyamaz]

In a few hours I'll be uploading Monster 1.0.7 due to about 5 configs being rolled backwards for some odd reason. Non of the mods themselves from 1.0.6 have changed at all, except one.

I am temporarily putting Open Blocks in as .disabled until we can figure out a fix for the issue with the Graves bug as this bug is quite critical. Though I have turned graves off in the configs, they are still spawning at player death, and players are unable to get there inventory back. Turning them on in the configs still does not fix the loss of inventory issue.

DO NOT UPDATE PAST 1.0.5 IF YOU USE OPEN BLOCKS AT THIS TIME!

Issue resolved. big thanks to @meuqsaco for reminding me that OpenBlocks supports ID=0.
​

Changelogs will be available at the usual place once @VikeStep gets to them.

 

[Yusunoha]

thanks for the heads up, hope it doesn't give problems to too many people

 

[meuqsaco]

Set grave ID=0 and it will solve your problem

Edit: I'm glad I could help.

 

[Eyamaz]

Set grave ID=0 and it will solve your problem

Oh? I'll try this before I push the update.

edit: you sir. i thank very much. I forgot openblocks supported the set id to 0 code (wish all mods did this.)

 

[Niels Henriksen]

Oh? I'll try this before I push the update.

edit: you sir. i thank very much. I forgot openblocks supported the set id to 0 code (wish all mods did this.)

Are there any guidelines for writing mods used for FTB?

 

[Golrith]

What is the problem with the Graves in Open Blocks. Got that mod on my custom pack on my server and have no issues.

 

[Eyamaz]

What is the problem with the Graves in Open Blocks. Got that mod on my custom pack on my server and have no issues.

Nothing directly, we think it's a conflict with another mod in the pack.

 

[UnionCraft]

Is 1.0.7 the beta-stable version?

 

[pyRex]

Ok, now I have an issue since the Monster 1.0.5 update and also the unleashed 1.1.7 update. I am sure its something simple.

Since the Unleashed 1.1.7 update, all my external dimensions (nether, end, myst) are creating directories in the server root, instead of the world directory. Didn't think much of it until the Monster 1.0.5 update has caused the same thing.

Apologizes in advance if this isn't in the right place.

pyRex
Feed The Bees Gaming
http://www.ftbees.com

 

[devryb]

Ok, now I have an issue since the Monster 1.0.5 update and also the unleashed 1.1.7 update. I am sure its something simple.

Since the Unleashed 1.1.7 update, all my external dimensions (nether, end, myst) are creating directories in the server root, instead of the world directory. Didn't think much of it until the Monster 1.0.5 update has caused the same thing.

Apologizes in advance if this isn't in the right place.

pyRex
Feed The Bees Gaming
http://www.ftbees.com

https://github.com/MinecraftPortCentral/MCPC-Plus/issues/480

 

[pyRex]

https://github.com/MinecraftPortCentral/MCPC-Plus/issues/480

I don't think you read either my post, or the link you replied with. My post stated this didn't happen until the mod pack updated. Still using the same MCPC release. As for your link, the origianl poster had this same issue with a recent update to DW20 1.6.4. Onibait related this to qCraft, which was a totally different issue all together.

Something in the recent mod pack releases is causing this.

 

[devryb]

I read both......................

You're right it was something recent.
Maybe you should look at the changelogs for the modpacks next time before accusing me of being the one that doesn't read........

Monster:
- Added qCraft
https://feedthebeast.atlassian.net/wiki/display/PML/Monster+1.0.4

Unleashed:
- Added qCraft
https://feedthebeast.atlassian.net/wiki/display/PML/Unleashed+1.1.5

 

[pyRex]

I read both......................

You're right it was something recent.
Maybe you should look at the changelogs for the modpacks next time before accusing me of being the one that doesn't read........

Monster:
- Added qCraft
https://feedthebeast.atlassian.net/wiki/display/PML/Monster 1.0.4

Unleashed:
- Added qCraft
https://feedthebeast.atlassian.net/wiki/display/PML/Unleashed 1.1.5

My apologizes. I failed to actually look at the contents of the new folders, instead I assumed(we know where this gets ya!) it moved everything there when actually I noticed that those folders only contain qCraft files. Looking back, I could have swore that this was addressed in the first patch for qCraft. Now I can't seem to find that information. Thanks for enlightening me.

 

[AlanEsh]

Oh? I'll try this before I push the update.

edit: you sir. i thank very much. I forgot openblocks supported the set id to 0 code (wish all mods did this.)

What does this mean? If you set a block ID to 0 (in some mods) it disables that block/feature?

 

[Tristam Izumi]

What does this mean? If you set a block ID to 0 (in some mods) it disables that block/feature?

If the mod supports such behavior, yes. Otherwise it just starts throwing errors and/or crashes.

/me found this out the hard way when he tried disabling HarvestCraft's cotton that way.

 

[Ashzification]

Thanks @Eyamaz <3

 

[Gizmo900]

Can you soon make it so the mod loader for MAC ' s don't crash instantly cause i can't seem to play and the terminal trick wont work for me either...Plz

 

[Ashzification]

Can you soon make it so the mod loader for MAC ' s don't crash instantly cause i can't seem to play and the terminal trick wont work for me either...Plz

If you're doing "the terminal trick" you're doing it wrong. You should be using Java 7.

 

[SatanicSanta]

Can you soon make it so the mod loader for MAC ' s don't crash instantly cause i can't seem to play and the terminal trick wont work for me either...Plz

I can run all of the FTB Packs perfectly fine. Install java 7.

 

[Elvanos]

Oh? I'll try this before I push the update.

edit: you sir. i thank very much. I forgot openblocks supported the set id to 0 code (wish all mods did this.)

Just an off-topic question. Is there a way to tell right off the bat if a mod (any mod) supports that feature or not?