I am here today with an update. The fact that this is exactly one year after the last release is actually a coincidence.
I’ve put together two elaborate patch documents describing two things regarding this release:
A changelog thoroughly describing the majority of changes between the version from one year ago and the version today
An explanation of the newly added difficulty modes—Hard Mode and Elite Mode!
Both of these can be found in the patch folder that’s linked in the OP.
I acknowledge that even last March’s release still wasn’t in the best state for presentation, and I apologize for letting it sit like that for so long. A lot of thought and consideration has gone into today’s update—through both past feedback from people outside the development team and new and innovative ideas from inside. Advent and I believe Forseti’s Cut has finally reached that point where the only thing that needs to be done from here is further writing and revision for the conversations original to FC. Of course, gameplay tweaks aren’t over either, but I’m hoping that this today feels like a complete, full release. The angles were thought out, and the gameplay can once again stand on its own two legs. Advent’s been a diligent playtester, so any new bugs should have been caught. If not, for some reason, I’ll try to be speedy about making the fixes for them.
I give thanks to the people who’ve lingered around in the Hacking Hel server, occasionally prodding their head and showing eagerness to see the next thing come out.
There was a critical bug causing the game to be unplayable in chapter 11x. The patch is updated to address that as of now, and includes one other change that was in the works—a revised in-battle graphic for Bragi’s Blade.
Yes. The Dropbox link in the OP is the only spot I’ll ever have the patch. You can see the last modified date for it, 3/6, for further reassurance.
Just make sure that, since they exist as two separate (but equally up-to-date) patches, you read HardModeAndEliteMode.txt to decide whether you want to play on normal mode (patch your Japanese unheadered ROM with FC1-2.ips) or hard mode (patch your Japanese unheadered ROM with FC1-2HardMode.ips).
I apologize if this is an overly silly question, but was it ever documented how exactly the Accost skill was changed in this hack to not activate when it doesn’t benefit its user? I looked everywhere and have not found anything.
There’s just an additional check in the code (with the HP and AS checks) to make sure that the unit with Accost can attack in that combat, meaning they have actual values for Atk, Hit, and Crt in the combat UI, and they’re not “- -”.
Or by “documented,” do you mean the actual edited code in ASM?
Yeah, the actual edited code, as in where and what the addition is. Of course, if it is supposed to stay an exclusive thing to the hack, then I fully understand.
The two additional lines were done by Ultimage, and the whole routine was edited with the help of his documentation.
The original routine is at $01D66E ($83D66E mapped), and for Forseti’s Cut, it was repointed to freespace, $4C1400, to make room for the added check. Assuming you’re looking at it (the freespace address) in a hex editor, these are the two added lines:
$BD 4E 00 - An lda command checking that the defending unit with Accost will attack in the combat
$F0 17 - A beq command that’s right after
The project does have a GitHub, but since I’m the only one who deals with it these days, it’s quite disorganized; there’s things like outdated/incorrect labels, stuff without proper comments, and poorly placed stuff. There’s no real rhyme or pattern behind my usage of freespace. You’re welcome to take a look, but I figured the above documentation I gave was somehow more proper.
I am back with an update—version 1.3! And it has a proper checksum this time.
Other than thanks to Advent and Louie for their continued asset production, I don’t have too much to say. For detailed changes on this latest patch, refer to FC1-3Changelog.txt. I also did a retake on the OP for this thread.
The main incomplete part of the project is still the added dialogue. New drafts and revisions have been in the works since the release of FC 1.2, and now up until chapter 14, it should largely be up to snuff. I hope you have a fun time playing!
Hello again. Another update—version 1.31. This comes with several more gameplay and dialogue tweaks, as well as fixes for a couple minor bugs, though the most notable bug was something regarding Resilience, the one new skill.
Added a new changelog file for 1.31 that is separate from 1.3, as well as different names that appear within the checksum based on which patch difficulty you select.
Shannam didn’t spawn during chapter 15 for me. I assumed this meant that Mareeta learning Astra was now locked behind the B route but I got to him in 16B and she can’t talk to him before or even after his recruitment. Any idea what went wrong?
Not really, unfortunately. I reviewed the event code for his spawn as well as checked it out in practice on my own end, and everything seems to be as it should. I can’t do much without further information. If you have a recording or a .srm for right before it’s about to happen, either would be helpful.
Shannam spawns on NPC phase of turn 10, and the event was otherwise altered just so that he can’t be blocked even if another unit is on that fort tile. The only ways I can see missing him are by completing the map within 10 turns; being at the enemy cap (50) when he’s supposed to spawn, thereby preventing his spawning (which is technically possible but extremely unlikely because of the chapter’s NPCs); or fast forwarding through enemy and NPC phase during the turn he spawns and not realizing that an NPC (most likely Amalda) actually killed him. In the future, I plan on having Shannam appear in gameplay during chapter 14, after he talks to Homer to say he’s leaving Tarrah, to give the player a second chance to have Mareeta talk to him.
Normally I could have waited a while longer before putting out another update, but I noticed something quite wrong in chapter 12x the other day, so I wanted to provide a fix for that as soon as possible.
