Development

Week 11 has been about the development of the vendor system as well as about the start of the combat implementation.

In a sense, it has been a difficult week. The implementation of the vendors and trade system has revealed a significant flaw in the execution of the UI code. This flaw doesn't affect performance or user experience, but does affect coding performance (in the sense that it is written in a way that would take very long to debug/adapt to new systems).

this flaw has also been detected in other UI systems implemented so far and will be fixed for all of said systems during the first big refactoring window, which is to come at the end of the development of the main, "over-arching" systems of King For A Week.

In another sense, it has also been a good week. Despite the detection of the aforementioned flaw, the trade system is currently working. The backend code is running without a hitch and the full Item system is also adapted to the game's requirements. Moreover, the combat philosophy of the game has also been defined. Fast-paced, 1-st person melee and ranged combat, heavily ethos-defined with room for personalization.

In the coming week the combat system will be refined, allowing for the equipping of weapons (going beyond the simple system already in place), the creation of combat configurations (using multiple weapons at the same time), skill trees and many more exciting features.