Welcome to the AFK Mods bug tracker. In order to report an issue, you need to have a VALIDATED account to post one. Once you have followed the link the registration email sent you, please select a project from the drop down menu below. Select “Open New Issue” and fill out the form with as many details as possible.

Please also consider sending your bug report to Bethesda if you are reporting on an issue with Skyrim Special Edition, Fallout 4, or Starfield. Doing so will help everyone on all platforms.

Issue Data
Status: Closed
Issue Type: Bug Report
Project: Unofficial Fallout 4 Patch
Component: Fallout 4: Vanilla
Category: Text
Assigned To: BlackPete
Platform: All
Severity: Very Low
Votes: 0
Watching: N/A
Opened By Iniquitatis on Aug 23, 2020 12:23 am
Last Edited By BlackPete on Aug 31, 2020 2:12 am
Closed By BlackPete on Nov 25, 2020 4:15 am
Resolution: Fixed
Comment: Fixed for UFO4P 2.1.2 (as noted in my last comment).

Issue #29240: More typos

 
1. Talking with MacCready after killing Winlock and Barnes: *Laughs*;
2. Quest stage of the Long Road Ahead: "Continue Traveling with MacCready";
3. Father's terminal in the Institute: double space.



Attached Files:

11172154181194612736_20200821155450_1.png
11172154181194612736_20200821155656_1.png
Jammed Spacebar.png

Comments

4 comment(s) [Closed]
Iniquitatis said:
 
By the way: is there any way to extract all text/strings/whatever in the Creation Kit (FO4Edit?), so it could be reviewed in a separate application? Because it would be infinitely easier to deal with such issues in a one big batch.

Iniquitatis said:
 
I've written a script for FO4Edit, which exports strings from the quest dialogues and terminals. Now it is easier to find common errors, such as *Blah*, Dima, etc.

Comment #2 Aug 23, 2020 5:32 am  Edited by Iniquitatis on Aug 23, 2020 5:34 am
BlackPete said:
 
To answer your question, there is apparently a dialogue dump function somewhere in the Creation Kit. I'm not exactly sure where it is and how to use it. The downside is that it won't be of much use in correcting typos because there's no way to re-import updated text afterwards.

While the CK text dump method and the FO4Edit script method you mention are great for making it easier to identify these errors, any corrections absolutely need to be done in the Creation Kit. Several potentially serious problems can arise from making text corrections using FO4Edit. Just thought I'd mention that in case you were thinking of providing fixes for the project for some reason. If you're only planning on using the script to identify and report bugs for us to fix, then there's no need to worry about what I just said.

Comment #3 Aug 24, 2020 1:31 am  Edited by BlackPete on Aug 24, 2020 1:45 am
BlackPete said:
 
As far as the fixes go:

#1: This was handled in Issue #29244.

#2: Arthmoor has asked me not to alter capitalization inconsistencies in quest objectives like this (they were bothering me, as well). He said since they're generally not complete sentences, he doesn't want to get into making changes to them unless words are actually misspelled. I think another part of it is that there are far too many objectives in the game and he doesn't want to make so many changes to these types of records in the patch. On the other hand, quest stages are always complete sentences, so those are fair game as far as fixing incorrect or inconsistent capitalization.

#3: The double space has been corrected in the terminal entry.

Comment #4 Aug 31, 2020 2:12 am  Edited by BlackPete on Aug 31, 2020 6:43 am
Showing Comments 1 - 4 of 4