Blacksmith Day Count Bugs Across New Year
Rybec opened this issue · 17 comments
Harvest Festival 0.6.0-218 (the latest version on Curseforge at the time of writing).
Two days before New Years, I gave the blacksmith a silver hammer to upgrade to gold. The day before, he said there was 1 day left. The day after, he says 120 days. I waited another day to make sure, and now it says 119 days. I suspect I could get it back by setting the season length to 31 days, so that there are more than 120 days in the year, but then I have to wait almost 120 days, before I can use the blacksmith again.
@Rybec when the bug first occurred, had you changed the amount of days a month, or ticks per day in the config?
@Rybec were you playing on a server?
That is very weird. Tried to reproduce your issue with the steps you provided a couple of times, and wasn't able to.
If you have time, could you try out the latest Jenkins build from here: http://girafi.dk/jenkins/job/Harvest%20Festival/job/Harvest%20Festival%200.6.X%201.10.2/
Maybe something we changed fixed it?
Would appreciate the mod list :)
You could upload it to Imgur, Dropbox or something like that, and link it here, since I don't think you can attach images to comments.
Thanks for the list, appreciate it. I will test it out tomorrow within a couple of days.
Sounds good!
I just tried it a couple of times again, with upgrading a silver hammer to a gold hammer 2 days before new years. With the mod list you provided of course. And still not able to reproduce unfortunately.
Closing this for now, but if you can still reproduce this with the latest Jenkins build, please let me know and I will take another look :)
Well, that did not work. I changed the season length to 31 days. Now the blacksmith says it has 130 days left.
Alright, I changed the season length to 10 days. That got me my hammer back. (Since increasing seasons by 1 day, which only adds 4 days to the year added 10 days to the wait time, I figured lowering it might take off more than expected as well.)
Anyhow, this is an effective workaround, if anyone else experiences this issue. It does not seem to have caused any new problems.