Project Arkavite [0.2.0-A]
Changes:
• The game background will now blur on pause and the system menu button will now pause the game.
• Minor texture improvements have been made to the main menu, and the Credits page has been updated.
• I've made substantial changes to the player, lighting and shading in order to reduce smear and artifacts and have tweaked the face normals to make the shadows appear more stylized and less icky. This is a more significant change for the sandbox environment where lighting is less controlled, but now these changes have been made, I can increase the priority of implementing those preview environments for the character creator.
• There have been some further optimizations. The Character Creation level has had its complexity reduced. I've also added aliasing method settings which will offer an additional boost in performance should you choose to lower the default setting.
• Fixed issue where Hair attachments and tail shading did not match the base hair shading.
• Fixed issue where dropdown choices in the character creator did not enforce selection limits. Code to handle this has now been implemented.
• Fixed bug: [Luck Stat not appearing in character creator]
• Fixed bug: [Sliders Do Not Reflect Model When Returning to Character Creator from the Menu]
We're a bit of the ways out, but for the next public build I would like to do some more modelling and texturing. Glasses and eyepatch options are at forefront of my mind. Updating the male outfit and adding some more hairstyles is also high priority. I'll see what I can fit in between sandbox work.
This week I will be working on the command framework which is the backbone of the games item, event and TF system. We've already made quite a lot of headway with the inventory, stat screen and reflection screen but there is still more to do. I'm aiming to get the HUD working and once the command framework in place, begin testing items on the backend. That will probably fill the next few weeks, but after this, we can finally crack on with combat.
Swords or guns? I wonder what I should start with first.
• Minor texture improvements have been made to the main menu, and the Credits page has been updated.
• I've made substantial changes to the player, lighting and shading in order to reduce smear and artifacts and have tweaked the face normals to make the shadows appear more stylized and less icky. This is a more significant change for the sandbox environment where lighting is less controlled, but now these changes have been made, I can increase the priority of implementing those preview environments for the character creator.
• There have been some further optimizations. The Character Creation level has had its complexity reduced. I've also added aliasing method settings which will offer an additional boost in performance should you choose to lower the default setting.
• Fixed issue where Hair attachments and tail shading did not match the base hair shading.
• Fixed issue where dropdown choices in the character creator did not enforce selection limits. Code to handle this has now been implemented.
• Fixed bug: [Luck Stat not appearing in character creator]
• Fixed bug: [Sliders Do Not Reflect Model When Returning to Character Creator from the Menu]
We're a bit of the ways out, but for the next public build I would like to do some more modelling and texturing. Glasses and eyepatch options are at forefront of my mind. Updating the male outfit and adding some more hairstyles is also high priority. I'll see what I can fit in between sandbox work.
This week I will be working on the command framework which is the backbone of the games item, event and TF system. We've already made quite a lot of headway with the inventory, stat screen and reflection screen but there is still more to do. I'm aiming to get the HUD working and once the command framework in place, begin testing items on the backend. That will probably fill the next few weeks, but after this, we can finally crack on with combat.
Swords or guns? I wonder what I should start with first.





Here is my first commentary on the design, answering many questions you have now. It is not a to-do list. It is what gets you "value" for your time and makes your game better.
The most important thing you can do to make your game not shallow is to design the distributions of probabilities for your world carefully from the start.
1. Work out an approximate geology, this can be even 50% wrong, as in the sense of if you now draw an area that is a map, half of area could be something else or somewhere else.
Perhaps a month to experiment and study how to use DF engine to adapt it to your world as accurately as possible, e.g. remove unnecessary races, figure out that if magu would map to elves (heuristically, only) what would everything else map to, how to make DF to emulate your magic and divinity systems. DF engine will do the heuristic simulations. Make a single map that is as perfect as possible.
You can then use Simplex noise, your own algorithms to approximate where floating island etc. should go.
Now you have a realistic, in both IRL sense and in-world sense, *heuristic map.*
You would also have possibly some direction, inspiration for larger geopolitical directions where the world could be developing toward during gameplay from DF history. Story wise DF will sort of take care of "which civilizations would probably contact each other" and "who would become the traders that cahrge lots because others have poor soil" and you can then adapt from that, perhaps Ikaware are thriving in such places especially near rivers and sea, and you would make such dwarf civilizations Ikaware.*
2. Once a heuristic, adapted map exists, you can start working on some 3D things very aggresively, because you know how the geology looks like and how cities more or less look like, and the work is mainly adapting the map to the 3D world which can be rather creative and enjoyable. What would this or that dwarf bar be named if it were by made Nya-Nyaatsu? How would this Bunjinn house be decorated as? And then just move to next house because you have good approximation where it should be.
3. Any single "person" you have will be made out of many factors from charachter gen factors to personality.
In real world, human can be mapped into distributions that make up Bayesian stochaistic processes, and you want to generate like daitributions for your world.
Three examples:
A: Define the personality distributions for Magus. Define age distributions for Magus. How does age generally affect personality? Are very young Magus more shy? Then in generation, young magu, that we are now generating the personality for, should have higher propability to become shy, than if it had become an adult one.
B: It's unlikely that there is the exact same amount of gay everywhere. How does that vary with race and location? In an area with many gays, there should be higher probability that there are adult teen and adult gay charachters that have moved to that area.
C: IQ probably has a distribution. IQ goes with wealth. But probably not equally for all races. High IQ charachter or a race that is discrimated somewhere should then have less probability to get rich with business.
There are very many distributions, and you want to define these as comprehensively as possible, and to connect them all to each other. Only then you should move to design of invididual charachters, highlighting and developing the charachters the player will probably enjoy the most.
Designing the distributions and the stochaistic processes they generate well is only way to make a an immersive, deep and large game. If you don't do this you will just be wasting years of your to realize that you should have done it.
4: A more important point: The only way to make a REPLAYABLE open world is to combine stochaistic models with delayed branching. LLMs may have made this interactive fiction technique bit more outdated than it was in 2014. But it remains highly relevant.
Stochaistic processes are the processes that control how the world evolves.
Delayed branching will take into account how the world evolves but always return to certain inevitable storytelling parts. It's a way to write a good IF plot without having to write exponentially more passages for an expanding choice tree, of the kind used in many of the earliest IF.
My email is [email protected] if you want to get in touch.