Alpha-Advanced Phase

Published March 11, 2024

After successfully completing all previous steps in the Action Plan, despite being an extremely small team, we have achieved our goals with effort and dedication. Some challenges were overcome in record time, while others required more time to resolve. We have always prioritized quality and addressed any issues immediately.

Launch of the Main NFTs Market: The Main NFTs Market is also among the most anticipated features. This is a complex market because it has its own rules. Additionally, it should provide you with all the relevant information about the horse NFT you are about to purchase. You might prefer to buy a healthy horse over a sick one, or you might be carefully reviewing the statistics, costs, and know what is most advantageous.

Announcement of NFT Factories: We will advance this system a bit because, as you may already know, BHR is not like other blockchain games, and we have demonstrated this on several occasions. This system is designed to enhance the game in a very blockchain-centric way that we all love. Who doesn't like combining 2 NFTs to directly get something better with a higher value? This is exactly what you can do in a factory. Imagine burning 2 apples to get a food item that gives double the mood points to your horse, or burning two bales of hay to get a base food item that not only gives double points but also allows you to multiply your horse's mining throughout the season. We believe this type of feature would benefit the game and will be something that only a few privileged players will be able to obtain. Although all game users will have the same opportunities to acquire a Factory, keep in mind that there will only be a maximum of 2% factories relative to the total horse population. In this case, there would only be a maximum of 8 factories for 400 horses, and so on as the population grows. Note that the 2% is the maximum, but it is not mandatory to fill all slots.

It is important to understand that although all the points to be worked on during this phase are represented here, they are not in a specific order, nor do they have a specific activation or completion date. It is well known that taking the time to properly prepare features is better to avoid issues that later generate more time lost in support than in improving the same code that caused the error.