Game Update Information The mod uses signature scanning to find the correct address for the patch. It doesn't need updates until SFSE refuses to load it or it stops working after Bethesda changes the code I modify, in which case I have to change my code as well. However, the SFSE itself must be updated after each game update! Make sure to update the Starfield Script Extender (SFSE) for the version of the game you're using before reporting that the mod is not working.
Users of the ASI Loader version don't have to care about updates until the mod stops working. But, if you use the bink2w64.dll of the ASI Loader, each game update will overwrite the DLL with the original one. Make sure that your ASI Loader is installed correctly after each game update.
Thanks to the byte pattern signature scan, the mod verifies the integrity automatically, therefore it should never crash your game, if the code mismatches after a game update. It will simply stop working.
Bug Reporting First of all, make sure you don't use an older or a different version of the mod. Especially if you've installed my fixed version from GitHub before, you should delete the Starfield-LongerNames.dll or uninstall it with the mod manager!
If you're 100% sure that you're using the right SFSE for your game version and you still have trouble with the mod, please provide following information, if you want to report an issue.
Your game version and update version (Steam/GamePass/Cracked, version 1.7.36 etc.)
Which mod version are you using, SFSE or ASI
Your installation method, if you're using Vortex, MO2 or manually.
Provide content of log files. For SFSE all logs should be in the Documents directory (C:\Users\(windows user name)\Documents\My Games\Starfield\SFSE\Logs\), there I need the content of sfse.txt, sfse_loader.txt and SF-LongerNames.log files. For the ASI version, the log file should be in the mod DLL directory (default (game root)/Plugins/).
This mod has issues with Starfield Update 1.14.74, and the SF-LongerNames.toml file is the issue as no other mod uses a toml file. This might be the issue why SFSE crashes all of the time and only way around the issue is to uninstall Starfield and delete all files then after a reinstall SFSE runs correctly.
I highly doubt it. The only issue toml or any configuration file can cause is that the game has no permissions to access it and the mod uses default value. Could access right on toml file cause a crash? I can't completely rule it out, but then the question is why doesn't the game have access to its own directory on your system? The last update was last year in November, I tested it and comments below confirm that it works. You also failed to provide me with the information I asked for in the “Bug Reporting” section of the mod description. This is a sign to me that you have not read the Description.
Thanks for this mod. I was originally playing on Xbox and I was able to name my ship "To Seek Glory in Battle is Glorious" but when i made the switch to PC was disappointed that I was limited to "To Seek Glory"
Woohoo, still working as advertised, with latest/current game version 1.12.36 ! \o/
Hella nice work on this, igromanru! Kinda silly that modified items end up with long-ass (vanilla) names, yet we're limited to only 26 characters if we want to rename stuffs, pfft!
Workin' awesome! (SFSE version, Steam, Manual install) THANK YOU for this! Endorsed! ♥
EDIT: Still working hella fire, with the new Starfield Update 1.13.61 ! o7 ♥
So the Plugin still works with all game versions. ASI Loader now only works with bink2w64.dll. I've updated the ASI Loader installation steps in the Description page.
ASI version doesn't seem to be working (GamePass). I installed it manually (assuming it goes in the /Content/Plugins folder like any other ASI plugin I've used), and I tried to name a ship "Independent Systems (something, hadn't figured that part out yet), and it wouldn't allow me to enter past "Independent Sys" or thereabouts.
I've hard time to support the GamePass version, because I don't have it. Can you please provide more information? Where exactly is the /Content/Plugins folder? In the Steam version there is no Content folder, I've tested asi mods to be loaded from the game root directory and the (game root)/Plugins/ directory. (EDIT: Nevermind, I saw the description in Achievement Enabler) But if you say that other asi get loaded right from the /Content/Plugins folder, it should work as well. Can you please name few asi mods that you're using and are working for you? So I can check them out, what they are doing.
Also can you please try to rename a weapon, spacesuit or something and see if you get a very long name with more than 26 characters? It would confirm that the mod isn't working at all.
EDIT: Can you please try out the version 1.0.0 of the mod, but only with ship names or outposts. If it works for you, I might know how to fix the version 2.
EDIT2: I found someone who told me how it works. The asi file has to go either into the game root directory (same folder as the Starfield.exe) or the (game root)/Plugins/ directory.
/Content/ is the game root on Game Pass. I haven't had a chance to test what you asked yet, but I'll download the update, test it, and try the older version as well to be sure.
Re: what other ASI plugins I'm using, I thought there was more, but the only one I have is Disk Cache Enabler because I'm playing from an older computer/HDD so it helps mitigate the excessive load times and freezing/stuttering, but other ASI plugins I've looked at, can't remember which specifically, also say to install to /Content/Plugins (which, as I mentioned in my previous reply, /Content/ is the Game Pass version's root folder, the exe, Data folder, and all the other files are there).
Additionally, a lot of the addresses are apparently different between Game Pass and Steam, if that makes a difference for ASI plugins. There was another mod (I can't recall which one, unfortunately, I don't think it was an ASI plugin, so this may not be relevant depending on how ASI plugins work) had an issue where it was supposed to work on Game Pass or Steam but it was only working on Steam, they had someone send them a zipped file of the entire Game Pass Starfield folder, maybe someone could do that for you (I would, but I don't remember which files are mods and which are vanilla anymore, and I'm not willing to return to a vanilla install and have to find and redownload all my mods for this) if that's relevant, and you can use that to figure out how things work with the Game Pass version.
The mod is finding the right address by himself. It shouldn't be a problem. And you're so far the only one reporting that ASI doesn't work. Please try out the latest version 2.0.1 and then tell me what does the log says. The SF-LongerNames.log should be in the same directory as the mod asi. If there are no log files, it could be an indication that the mod is not loaded. EDIT: Also a very good indicator if the mod was loaded is the SF-LongerNames.toml file. It should be created automatically in the game root directory.
It's not generating a log or a .toml, I'm not sure what the issue is, because the other ASI plugin I use, that enables disk cache, still seems to be working. EDIT: And this is with the newest version 2.01.
I let someone from the modding community with the GamePass version test the mod. He can confirm that it works. If the ASI Loader loads the mod, the mod creates a log file into the mods directory and the toml file in the game root directory. So I have no idea what are you doing wrong, but at this point I'm pretty sure that the mod simple doesn't get loaded by the ASI Loader. May I ask how do you know that Disk Cache Enabler works? Because it's not something you would notice easily, unless it creates a log file. Also which ASI Loader version do you use? Which DLL? winmm.dll and wininet.dll seems to work.
I know the disk cache enabler works because I can see that it works. As I mentioned before, I play from an HDD and an old computer, and before I installed that plugin the game was freezing for minutes at a time on loading a new cell, and just randomly during gameplay, and then after adding it it freezes for 5 seconds at most loading a new cell and not at all during gameplay. I'm using the bink2w64 version of the ASI loader, and the latest version of that, because I saw instructions (I think on a previous version of the disk cache enabler mod's description but it's since been edited so I can't see for sure) to get that version if on Game Pass version of the game and rename the existing bink2w64 file to bink2w64Hooked.
It's a little too vague for me. There are too many technical factors that can play a role why your game were freezing and doesn't do it anymore. It begins by a different location that is being loaded and ends by a possible fix that applied with one of latest game updates. At least it is not a concrete evidence that the ASI loader is working properly or that the mod is loaded. It's too subjective. I don't know how to help you, nobody else seems to have the same problem here and like I said, the mod were tested by someone who has the GamePass as well. The only difference that he uses the wininet.dll as ASI Loader. It doesn't require you to rename any other DLLs, just to put it inside the game root directory. At this point this is the only thing I can suggest, to try out a different loader version and maybe install some other ASI mods, to see if you run into the same problem. You can try out my other mod for example: Zero Weight Because if you don't even get the asi loaded into the game, there is nothing I can do about it.
And I guess I'm blind and extremely susceptible to the placebo effect. Turns out I didn't have an ASI loader installed anymore (apparently forgot to replace it when the game updated last), so I was using an old and a new version of the same, unmodified, bink2w64.dll file. Fixed that, and now the longer names mod generated the log and the .toml file, so it should be working, and maybe now I'll see some more/actual improvement in performance from the cache enabler mod as well.
;) Therefore I recommend to use a DLL as ASI loader that doesn't require replacement. They won't be replaced after each update. They work as well as the bink2w64.dll. bink2w64.dll just become an echo chamber. Someone tested it and told others to use it and now we have multiple mods using bink2w64.dll in their installation description, even though there are multiple working solutions. I'm just as guilty of it myself, until someone else told me that dinput8.dll (x64), wininet.dll (x64) and winmm.dll (x64) are getting loaded by the game. Therefore it doesn't matter which one you take. However, I'm glad I could help you.
46 comments
The mod uses signature scanning to find the correct address for the patch. It doesn't need updates until SFSE refuses to load it or it stops working after Bethesda changes the code I modify, in which case I have to change my code as well.
However, the SFSE itself must be updated after each game update!
Make sure to update the Starfield Script Extender (SFSE) for the version of the game you're using before reporting that the mod is not working.
Users of the ASI Loader version don't have to care about updates until the mod stops working. But, if you use the bink2w64.dll of the ASI Loader, each game update will overwrite the DLL with the original one. Make sure that your ASI Loader is installed correctly after each game update.
Thanks to the byte pattern signature scan, the mod verifies the integrity automatically, therefore it should never crash your game, if the code mismatches after a game update. It will simply stop working.
Bug Reporting
First of all, make sure you don't use an older or a different version of the mod. Especially if you've installed my fixed version from GitHub before, you should delete the Starfield-LongerNames.dll or uninstall it with the mod manager!
If you're 100% sure that you're using the right SFSE for your game version and you still have trouble with the mod, please provide following information, if you want to report an issue.
For the ASI version, the log file should be in the mod DLL directory (default (game root)/Plugins/).
Could access right on toml file cause a crash? I can't completely rule it out, but then the question is why doesn't the game have access to its own directory on your system?
The last update was last year in November, I tested it and comments below confirm that it works.
You also failed to provide me with the information I asked for in the “Bug Reporting” section of the mod description. This is a sign to me that you have not read the Description.
Confirmed working just fine as of 5th Feb 2025.
(using SFSE version, Steam, Vortex install)
(Using the SFSE version; Steam; Manual installs)
Hella nice work on this, igromanru! Kinda silly that modified items end up with long-ass (vanilla) names, yet we're limited to only 26 characters if we want to rename stuffs, pfft!
Workin' awesome! (SFSE version, Steam, Manual install) THANK YOU for this! Endorsed! ♥
EDIT: Still working hella fire, with the new Starfield Update 1.13.61 ! o7 ♥
Again, THANK YOU for this hella essential mod, igromanru! ♥
ASI Loader now only works with bink2w64.dll.
I've updated the ASI Loader installation steps in the Description page.
Can you please provide more information? Where exactly is the /Content/Plugins folder?(EDIT: Nevermind, I saw the description in Achievement Enabler)In the Steam version there is no Content folder, I've tested asi mods to be loaded from the game root directory and the (game root)/Plugins/ directory.
But if you say that other asi get loaded right from the /Content/Plugins folder, it should work as well.
Can you please name few asi mods that you're using and are working for you? So I can check them out, what they are doing.
Also can you please try to rename a weapon, spacesuit or something and see if you get a very long name with more than 26 characters?
It would confirm that the mod isn't working at all.
EDIT: Can you please try out the version 1.0.0 of the mod, but only with ship names or outposts. If it works for you, I might know how to fix the version 2.
EDIT2: I found someone who told me how it works. The asi file has to go either into the game root directory (same folder as the Starfield.exe) or the (game root)/Plugins/ directory.
Please try out the latest version 2.0.1 and then tell me what does the log says. The SF-LongerNames.log should be in the same directory as the mod asi.
If there are no log files, it could be an indication that the mod is not loaded.
EDIT: Also a very good indicator if the mod was loaded is the SF-LongerNames.toml file. It should be created automatically in the game root directory.
EDIT: And this is with the newest version 2.01.
If the ASI Loader loads the mod, the mod creates a log file into the mods directory and the toml file in the game root directory.
So I have no idea what are you doing wrong, but at this point I'm pretty sure that the mod simple doesn't get loaded by the ASI Loader.
May I ask how do you know that Disk Cache Enabler works? Because it's not something you would notice easily, unless it creates a log file.
Also which ASI Loader version do you use? Which DLL?
winmm.dll and wininet.dll seems to work.
I'm using the bink2w64 version of the ASI loader, and the latest version of that, because I saw instructions (I think on a previous version of the disk cache enabler mod's description but it's since been edited so I can't see for sure) to get that version if on Game Pass version of the game and rename the existing bink2w64 file to bink2w64Hooked.
It begins by a different location that is being loaded and ends by a possible fix that applied with one of latest game updates.
At least it is not a concrete evidence that the ASI loader is working properly or that the mod is loaded. It's too subjective.
I don't know how to help you, nobody else seems to have the same problem here and like I said, the mod were tested by someone who has the GamePass as well.
The only difference that he uses the wininet.dll as ASI Loader. It doesn't require you to rename any other DLLs, just to put it inside the game root directory.
At this point this is the only thing I can suggest, to try out a different loader version and maybe install some other ASI mods, to see if you run into the same problem.
You can try out my other mod for example: Zero Weight
Because if you don't even get the asi loaded into the game, there is nothing I can do about it.
Therefore I recommend to use a DLL as ASI loader that doesn't require replacement. They won't be replaced after each update. They work as well as the bink2w64.dll. bink2w64.dll just become an echo chamber. Someone tested it and told others to use it and now we have multiple mods using bink2w64.dll in their installation description, even though there are multiple working solutions.
I'm just as guilty of it myself, until someone else told me that dinput8.dll (x64), wininet.dll (x64) and winmm.dll (x64) are getting loaded by the game. Therefore it doesn't matter which one you take.
However, I'm glad I could help you.