Page 4 of 4

Re: Change Tracking & Bug Reporting Thread

Posted: Sat Dec 10, 2016 4:25 am
by Daigle
I thought I heard that eggs are working on spawners again but when I try it, I get a message that says "Successfully changed the spawner to a 0 spawner" and it no longer spawns anything. I tried it with a generic "Monster Spawner" and also a "Skeleton Spawner" with the same result... both times with a sheep egg. Also, silk touch doesn't work on them either. I know this is probably beyond your control but I figured I'd mention it.

Re: Change Tracking & Bug Reporting Thread

Posted: Sat Dec 10, 2016 2:45 pm
by Pri
It's due to the spawner being before 1.11 - It appears they all need to be re-purchased and re-placed. We will investigate more.

Re: Change Tracking & Bug Reporting Thread

Posted: Tue Dec 13, 2016 3:23 pm
by Daigle
The quickshop chests in the admin head shop at spawn do not seem to be working. The nearby player shops work fine, it just seems to be the head shop. When you left-click the chests, they do nothing.

Re: Change Tracking & Bug Reporting Thread

Posted: Tue Dec 13, 2016 10:22 pm
by Pri
Yeah I'm not sure whats up with them but we need to remake any shop that was unlimited I think. Another 1.11 bug lol

Re: Change Tracking & Bug Reporting Thread

Posted: Mon May 29, 2017 4:45 am
by freakboy31
Pri wrote:
Tue Dec 13, 2016 10:22 pm

Hello, I cannot upload a midi file into the Files page. it says it worked but the midi "mitaka5" didn't appear in files list and I can't play it in minecraft.

Re: Change Tracking & Bug Reporting Thread

Posted: Tue May 30, 2017 11:49 am
by Pri
I just uploaded one to test it and it uploaded successfully without any problems. Perhaps the one you uploaded was malformed or the upload was interrupted in some way?

Re: Change Tracking & Bug Reporting Thread

Posted: Sun Jul 30, 2017 12:31 pm
by frostysss
I was able to fly in a
egg: hard mode,

Re: Change Tracking & Bug Reporting Thread

Posted: Wed Aug 09, 2017 1:07 am
by Pri
Hey Frostsss thank you for your report, we believe this issue has now been corrected :)