Fates Weekly Update #30

Hey, folks. Chief here with your weekly update. Are you in a good mood? I’m in a good mood. I’ve finally recovered from my illness and get to return to my flying job next week! That means I can get back out there earning and saving money that can be used to increase the amount of awesome things in Fates! That, and I hate sitting at a desk. The old man isn’t one for sitting at home living a 9 to 5. Those stories of excitement and adventure you all enjoy have to be inspired from somewhere, right? Until then, let’s talk Fates.

Wordcount: (6,010; Focused a lot on finishing up Act 2 as quickly as I can. I really want to get off the Planet of the Elves and continue my journey. A lot of focus this week was on the investigation sections of Act 2. Though this may come as a shock to you, I’m an old hand at Phoenix Wright games and enjoy them a lot. One thing that bugged me about Phoenix Wright though is that there is always only a single correct answer. A specific line and a specific piece of evidence is needed to move things along. I get it at points, but there were several cases that had me banging my head against a wall because I had a clear cut solution and the game didn’t like it.

I’m going into this with the idea that there should be multiple solutions to a particular investigation, multiple clues that could answer your mystery or take it on a completely different path. Act 2 is the first point where the clues and how you react to them will influence the story. A particular moment I want to share involves Lenna Edeck, Sol and Faye’s old love interest. During the course of talking with her, there will be several moments where you can use clues gathered to either realize that Lenna isn’t sharing her facts. Pressing too hard, however, can turn Sol against you pretty quickly. He still loves Lenna, and if you want to press her too hard, you can expect the investigations with him to be a lot more difficult. That does increase the amount of writing I have to do though, which is why I’m considering that additional writer.

Art: Still working on the blinks and movements of the characters. I do have a pretty awesome thing to announce. Originally, we didn’t have a character sprite for Natalie. Much sorrow. The sprite artist wasn’t going to be able to finish her off. However, thanks to the awesome Geckos, who is doing those animations, we now have a sprite for Natalie. That’s right, you aren’t going to be forced to do all Natalie/Name scenes from Natalie’s perspective! It also opens the possibility of side sprites again. I’m really, really, really excited. A couple characters are also going to get additional outfits as well.

Sisters fated against each other...
Sisters fated against each other…

Advertisement: Speaking of Geckos and her art, if you have a few spare dollars, please consider backing her kickstarter for a pretty awesome visual novel called Brilliant Shadows. I’ve gotten to do some admin support for it and I’m pretty excited about it. You can check it out here.

Voice acting: One last week to get your auditions in!

Lore: Now, for this week, we get to talk about something a little less… happy. While I do have some experience with chemical and biological weapons, I didn’t put a lot of thought into what hit Faye on that desert planet. I knew what I wanted to happen and lore didn’t really catch up. However, as her illness is going to be a pretty strong point in her route (dying tends to be a major life moment), it had to be worked out. Thanks to the help of the Eve writer, we now have a very detailed list of effects to what Faye is now suffering from.

Qudratexadon uses an ibotenic acid base to disrupt the lupide immune system, thus allowing it to take hold without being combated effectively. It causes inflammation of the alveoli, thus limiting gas exchange between the lungs and blood, and causing a buildup of fluid in the lungs. Qudratexadon poisoning directly causes effects to other parts of the body as well. Tissue hardening between brain hemispheres is a common symptom of Qudratexadon poisoning, and causes emotional turmoil, as the brain can no longer properly regulate emotion with reason (the effect is more profound in people that were predominately logical, as those mental tendencies are disrupted). Muscle development becomes hindered, and while the effect is generally universal, most cases are afflicted with uneven loss of muscle mass. In the worst cases, this can cause muscle spasms so severe they appear to be seizures, though most cases simply inhibit basic motor functions. Higher doses have a profound effect upon the nervous system, mainly damage to the nerves along the vertebral column and brain stem, causing impaired touch sensitivity, muscle paralysis, blurred vision, and possibly death.

I’d like to take a moment to mention that Faye is one of my favorite characters, she’s been in 3 visual novels so far. That being said, she is a very, very sick lupide who had the misfortune of ending up in a bad situation. Should she be out there? Definitely not, even with a specialist doctor following her around. Even though she’s a very lazy, very laidback person, Faye’s not going to abandon her friends in their time of need. Will Name be able to help her keep going or will Faye succumb to such a terrible disease…? Faye will be one of the hardest characters to keep alive in this story (both from external and internal problems), but you can do it.

With that bit of lore, I wrap this up for the evening. Remember not to contract deadly toxins! Until next time, Chief out!


Today’s video of the post is one talking about our new spaceship design. Kinda creepy that he does look a bit like me…

3 thoughts on “Fates Weekly Update #30”

  1. I wish I can fast forward through time to a point where this game is fully finish and I can buy it.

    I don’t wanna wait!!! DX
    I wanna romance Kika so bad!

  2. I enjoy reading and finding out more about Faye. Every passing week and everytime I read the next update makes me want to play Fates so bad.

Leave a Reply

Your email address will not be published.

Time limit is exhausted. Please reload the CAPTCHA.