As I wrote in #1 of this series already (here) we're currently focused to fix up small issues and to improve the gameplay and stability in general before we let the next big updates coming.
I, therefore, tackled 7 issues we had on our github to get our issue counter down a bit.
The pull request: https://github.com/Minecolonies/minecolonies/pull/2043
Let's run throught all of them like the last time.
#1: https://github.com/Minecolonies/minecolonies/pull/2043
Besides the main buildings there are "secondary buildings" like the scarecrow which, until now, was placeable anywhere in the world, I restricted this to inside the colony since players had issues with it.
I basically only had to add it to the list of blocks we check before letting them add to the world.
#2: https://github.com/Minecolonies/minecolonies/issues/2034
Some players were complaining that they thought a huge amount of raiders are falling into their colonies and only 2 arrived.
Therefore, we adapted the messages to give the player a feeling how many are coming.
So, I created 4 configureable categories of horde sizes which come with their own ID which toggle a different message.
#3: https://github.com/Minecolonies/minecolonies/issues/2042
A player reported problems with the builder wand after placing the camps.
Since, the camp and the ship are placed through the same interface the problem was that we didn't reset the variables accordingly after leaving it.
#4: https://github.com/Minecolonies/minecolonies/issues/1935
A player requested that there should be a more efficient way to access our workers inventories. At the moment you have to open their GUI and then click on the "inventory" button.
Now we detect if the player is sneaking (clicking shift) and then right clicks to directly open the inventories of players or buildings.
We get quite easily the value from the minecraft player object.
And then we just decide if we open the inventory or the GUI itself.
#5: https://github.com/Minecolonies/minecolonies/issues/2044
This one was easy to resolve as well, players were experiencing issues with the cook which seemed to throw errors.
The issue was that the entities of minecolonies occasionally lose their data, since they unloaded and will get it back only a bit later. Therefore, it can happen that we query a worker occasionally and the data is null. Therefore, we have to add a few saveguards there.
#6: https://github.com/Minecolonies/minecolonies/issues/1863
A player wanted a toggle all on or off button for the lumberjack GUI since else you have to click through all trees to activate or deactivate them.
#7: https://github.com/Minecolonies/minecolonies/issues/1776
This one didn't even involve coding, I only had to rename the files since the names were switched.
Which involved adding a button to the GUI and a buttonhandler to the code.
In the last issue I ran while debugging issue #6 after a restart I lost the permissions to access the colony. I found out that this was due to a synchronization error on the client side.
Therefore, I added to the code that besides "on change" it also randomly synchs every now and then.
Using a random variable to avoid that all colonies decide to do this at the same moment.
We already launched those chances and they'll hit our official modpack in the next 1-2 days as well.
Additionally we ported them to 1.10, 1.11 and 1.12.
I hope you liked the selection of fixes and quality of live improvements.
I'll see you the next time.
Posted on Utopian.io - Rewarding Open Source Contributors
Hey @raycoms I am @utopian-io. I have just upvoted you!
Achievements
Community-Driven Witness!
I am the first and only Steem Community-Driven Witness. Participate on Discord. Lets GROW TOGETHER!
Up-vote this comment to grow my power and help Open Source contributions like this one. Want to chat? Join me on Discord https://discord.gg/Pc8HG9x
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
Great work you're doing here. While I don't play Minecraft anymore this project looks really really cool. Thanks for sharing this.
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
Thank you for the contribution. It has been approved.
Games like this are a great gateway to programming. Keep up the great work.
You can contact us on Discord.
[utopian-moderator]
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
wow good information we need an update
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
Thanks for all the hard work on this, it will only get better.
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
Hey this will be great i think. So excited. Thank you for all the work.
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
good post @raycoms
and information that is very important to read
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
I really like your post
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
Sir this is very intresting post.
Exited for this gameplay. Before reading this artical.
I didn't know about that. But thanks to you for this outstanding informatioin.
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
worth sharing. Thanks
Follow + upvote Done
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit