- Aug 16, 2023
- 3,746
- 6,500
Done correctly the multiple MC skins should pretty trivial.I really want this game to succeed, which is why I'm going to offer the same unsolicited advice again.
CUT DOWN ON YOUR WORKLOAD.
If you insist on having two different versions of the protagonist, fine. If its your unshakable vision to have a staggeringly large amount of player choice, I understand. But you could cut your static renders down by well over half by just NOT overdoing a scene. For instance, the MC is sitting on a couch in one scene, there's some dialogue and description at the bottom, then he turns his head, more description, turns his head back, we hear his thoughts, sits forward a little, one more line of dialogue.
Now if you guys had a reasonably fast dev cycle, I would say that's fine (completely unnecessary, but its your perogative), but this game is three years old and it has less content than some games released just this year. You're good writers. For scenes that are not visually dynamic, its okay to have only a single render, or at least far less renders than your currently use and more words instead. Not only would this emphasize your writing abilities, but it would cut down production times, allowing for faster releases or longer chapters.
Food for thought. I'll keep supporting either way.
But I am not sure they are actually doing it correctly...
You also might have a point about unnecessary small static image changes during normal dialog.
Although one should not go over the top in trimming images.
And depending on how it is done it might not be too bad in terms of work.
I noticed there are some pretty redundant programming issues too.
After every choice there is an entire function for giving XP. which should have just been replaced with a simple function call.
like
giveCombatXP();
Also for some reason the white MC and black MC files are labeled differently. which requires code to load the correct image.
which is silly. just have 3 branches.
> code
> light
> dark
you make code changes in code.
then the light and dark branches can each automatically import those code changes and compile. (or manually if you don't want to set up automation)
when a new image file is added. add the light version to light repo and the dark version to dark repo. with same filename in same location. and watch as it auto compiles it.
Last edited: