Problems with the new tick-map-system
I’ve made the implementation of the furnace in Glowstone++ and now I want to check if everything is working with the release of 1.10.
And I noticed that that something go wrong with the tick map.
In a pull request the furnace looped tick request was converted to single request.
I don’t have anything against it, but it broke up the whole tick system for the furnace and maybe for some other blocks…
Because the new requested tick witch is added at the end of tickprocessing(https://github.com/GlowstoneMC/Glowstone/blob/master/src/main/java/net/glowstone/block/entity/TEFurnace.java#L148) is instantly removed through cancelPulse() in the pulseTickMap() (https://github.com/GlowstoneMC/Glowstone/blob/master/src/main/java/net/glowstone/GlowWorld.java#L1784).
Either for that cases (when the tick system broke up) we go back to looping tick or this issue gets fixed, that new ticks cloud be requested like that.
Niklas aka hibo98
@mastercoms said he was looking into this - A reply from him is pending.
Fixed now. Thanks for the heads up. I am sure everything else works, as I tested it before. I am not sure what happened to furnaces though. Perhaps I tested an earlier version which did work without testing a newer version of the new tick system which did not work with furnaces.
I see in the commit https://github.com/GlowstoneMC/Glowstone/commit/7f948567c05f6d623b33409623181c198c3e8a25#diff-394db2d2abc6fd2c27aca92d57d381bdL29 the tick request for already running furnaces on server shutdown/restart get removed.
Is that also a failure at your side or should these things handled different?
The new tile tick save format should handle that. It’s in a PR that will be merged soon.