-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Done setting up the config for spawned bugs" #18
Comments
Noted. Actually I have released an updated version that removes the spawning of the bugs on block break, that would include the debug logging. Thanks for informing though. |
Why'd you get rid of them completely? I have a lot of members who would scream at them. >_> |
Had problems with a lot of other users, but don't worry I'll bring them back in a different form. If you're copy of 1.4b3 isn't causing you too much trouble then I guess you can retain that version since there were no other changes done for 1.4b4. |
I'm glad some one appreciated the bugs.... ;) |
Many of my members won't appreciate them at all, that's the idea. >_> |
Oh ok.... lol |
sigh I loved the bugs too. They were great in my game where food is hard to find. "Hungry? Go dig for bugs" xD It was a lot of fun when someone screamed at the bugs though. For that reason, I'd make it a low percentage chance so that it was unexpected. Great for shock value :) |
the bugs will return along with a few new friends.... i just need to test a few alternatives. |
Done testing the graves by the way. I couldn't fault them at all. Even dying at the very top of the map in air or in the void. I've run out of ways to try to fault them. The damage options and death drop rules are working, including in my ~130 mod pack |
This is getting printed to the log with every broken dirt block, at least on the surface (including snow covering).
Seems a bit odd if that's what it's supposed to be doing, but even if not, it'd be nice to not have every single block break trigger a log event.
The text was updated successfully, but these errors were encountered: