If you get a "fatal error occurred while loading plugin" message for this mod while loading the game, try updating your vcredist to the latest version, or repairing an existing install.
Yes, we're super grateful. But many of us have concerns as popup messages and files suggest maybe it's not working, and it's not easy to validate given most of us already have a ton of achievements unlocked.
I mean if it didn't, then I'm sure shad0wshayd3 would say otherwise.
Yep, still works fine for me. With every major game update, I always test all the mods I use for compatibility, and report my findings. Also, whenever this mod BAE (Baka Achievement Enabler) gets updated, I reset all my achievements back to 0/62, via Steam console command, as well as confirming with SAM (Steam Achievement Manager). I started a New game and got the first achievement when you fly out into space for the first time, "For All, Into the Starfield".
Though I will admit, that my modded saves are now flagged with the [Creations] tag, but achievements are still unlocking fine, regardless. Whereas with the previous game version 1.14.74 and the previous BAE v5.1.0, the Creations tag was not present. Not a big deal though, so long as achievements are working fine, hehe.
The only mods I currently have installed (so far, but of course more will be added as they get updated) are:
Spoiler:
Show
Core-mods: Address Library for SFSE Plugins (updated for 1.15.216) Baka Achievement Enabler (SFSE) (updated for 1.15.216) Baka Disable My Games Folder (updated for 1.15.216) Starfield Script Extender (SFSE) (updated for 1.15.216)
Other mods: Baka Hold to Sprint (updated for 1.15.216) Enhanced Dialogue Interface (no update needed, still working) Enhanced Presets - Official Collection (no update needed, still working) Enhanced Subtitles (no update needed, still working) Native Ultrawide Menus - SFSE (updated for 1.15.216) Starfield 21x9 Ultrawide Fix LoadingScreens (newly released for 1.15.216) PerkPointsPerLevel (NOT compatible with 1.15.216; needs update) Player Eyes Stuck at the Dialogue Target Bug Fix - SFSE (updated for 1.15.216)
So if this mod (BAE) is not working for you, then there is something causing an error/conflict on your end. You may have a mod that needs to get updated for 1.15.216, which may be causing errors/conflicts. Be advised, due to the new 1.15.216 having made a lot of changes in the coding (from what I've read), almost (if not all) DLL-based mods (aka any/all mods that list SFSE as a Requirement) have been broken and will need to get updated for 1.15.216.
The reason we're politely asking if everything is ok, is because some of us see the popup, which we haven't for the past years.
"Creations are currently loaded. Note: Achievements are disabled."
Nothing disrespectful in asking for re-confirmation from author or from fellow gamers. We are all aware that this patch was a bit more impactful on SFSE, etc., as stated by Ian.
This is an intentional change that I made in version 5.0.0.
The intention was to make the mod more resilient by reducing the scope so that there's less of a chance for something to break between updates. Joke's on me, we had 1.14.74 for 6 months before the next update, so that didn't really matter- though it did help when 1.15.216 broke everything.
As far as I'm aware, you should only see the achievements warning when loading a save the first time you load a save game that was made without mods/a previous version of the mod, and after that it shouldn't pop up again, which I think is fine. The mod does continue to remove the popup when the console is opened, as well as the [C] tag on individual saves, which is the canary that lets you know it is working.
See it's not removing the tags on the saves which is what we are saying here. Once loaded, the save is considered modded and therefore an entire new save chain is created. The previous version, v5, when you first released it also suffered this problem but you managed to fix it. Please Please Please do so with this version.
The previous version, v5, when you first released it also suffered this problem but you managed to fix it.
I did not change this.
When I say "that was intentional", this is part of what I mean. When Starfield launched, the game worked similarly to other recent BGS games, in that the "modded save" flag really only affected the display name in the menu, and the AddAchievement function.
When Creations launched this changed and Starfield now uses the flag for some actual game logic while loading saves. I don't want to mess with that aspect of the game, and the actual point of this mod (Enabling Achievements) doesn't require this, so I think it's safer not to. This does mean that with the flag the Player ID of saves does change and they're in the separate (Creations) list. I don't want to separately try and mess with that aspect of the game either because I don't want the mod to cause any issues when it comes to creating new saves- making the game think it can't save, or overriding saves when it's not supposed to.
Having modded save files in its own "[CREATIONS]" section really isn't a big deal. If it means having this mod implemented in a way that it doesn't cause any problems/errors, then that is more desirable. Rather than not having modded save files in its own section, and having potential/possible errors/conflicts randomly happening. Thank you for the info, shad0wshayd3, and making that more clear. :)
I don't know if anyone can help me, but I've suddenly found upon updating that my existing saves are now being flagged with "Creations are present, achievements disabled" warning which I've never had with this mod.
Has this happened to anyone else since updating etc?
Edit 29.05 PM - I've loaded my existing saves and the usual creations warning came up in the main menu. I saved a new game & my game save was flagged with [C] for creations. However! I trialed an easy achievement and it still worked fine, so the mod works even though it gives warnings etc :)
Oh I never noticed your post at the same time! I've checked the bugs page and supposedly last year when loading saves it should still state the usual warning which we've received, but achievements will be unlocked regardless.
Though in my previous times using this mod, I never had this warning... so I kinda want somebody else to confirm this is supposed to happen too.
@otreb, well, I uninstalled and reinstalled both dependencies, while also uninstalling and reinstalling baka's achievement enabler. Still didn't work. Only other thing I could try is completely uninstalling all mods, and then installing just achievement enabler and its dependencies - I don't feel like doing that.
Behavior is, prompted that achievements will be disabled, and then when I test saving it after loading, the game did in fact create a new "character" that had that modded thing after its name. Presumably that means it's not working correctly.
I was lucky enough to have a simple one still locked (mod 50 weapons).
I loaded my usual save and used the console command to give me the weapons and mats, and went through modding all of the weapons until the achievement popped up/showed on my Steam page.
i triple checked install and am using vortex and make sure mods are deployed but everytime I try a new game is says creations are enables achievments are diabled. :-(
Hi, just a quick question. I installed the latest Baka Achievement enabler and when I load my game I still get the notification about the achievement. Is that normal? I'm currently on the last version of the game.
Hello,. Thank you for this mod and work you have done. I wanted to ask you would it be possible to post the 5.1 {previous) version as an older file option? I am unable to move forward to the newest version due to some incompatibilities. I don't know if it is problematic but it would be much appreciated if you were able.
At this point looks like Starfield is entering Skyrim territory where staying on a specific version is preferable to updating. Need the version of this mod that works with the previous version, where all things SFSE still worked.
The version available in the archive 5.0.0 (November 2024) should work fine with the previous version. It's the version I'm using now and have been using for over a month with the previous version. If an archived file is completely removed, it's probably for a good reason...
Looks like it still gives the 'Achievements are enabled' message. Installed it via MO2. Does anyone know if it still allows the achievements despite the message?
Interestingly it did get get rid of all the [C] that was on the saves, so maybe it still works?
Greetings and thank you for your work on this mod.
I have updated my SFSE, the Address Library and this mod, but when I go to load my game, I get the "Creations are loaded. Note: Achievements are disabled" message. I installed it via ModManager, which was how I always did before, then uninstalled it and reinstalled manually (yes to the same folder the Starfield.exe app is in) and same result. What am I doing wrong?
Yeah, seeing the same. Also tried disabling all mods and using the console. I didn't get the console warning message, but it did still mark my save. I did notice it was marked (Creations) and not (Modded). Is there a second check somewhere based off official creations now? I do have those original Bethesda ones enabled.
2488 comments
Yep, still works fine for me. With every major game update, I always test all the mods I use for compatibility, and report my findings. Also, whenever this mod BAE (Baka Achievement Enabler) gets updated, I reset all my achievements back to 0/62, via Steam console command, as well as confirming with SAM (Steam Achievement Manager). I started a New game and got the first achievement when you fly out into space for the first time, "For All, Into the Starfield".
Achievement earned! With Starfield Update 1.15.216 + Baka Achievement Enabler v6.0.0
Though I will admit, that my modded saves are now flagged with the [Creations] tag, but achievements are still unlocking fine, regardless. Whereas with the previous game version 1.14.74 and the previous BAE v5.1.0, the Creations tag was not present. Not a big deal though, so long as achievements are working fine, hehe.
The only mods I currently have installed (so far, but of course more will be added as they get updated) are:
Address Library for SFSE Plugins (updated for 1.15.216)
Baka Achievement Enabler (SFSE) (updated for 1.15.216)
Baka Disable My Games Folder (updated for 1.15.216)
Starfield Script Extender (SFSE) (updated for 1.15.216)
Other mods:
Baka Hold to Sprint (updated for 1.15.216)
Enhanced Dialogue Interface (no update needed, still working)
Enhanced Presets - Official Collection (no update needed, still working)
Enhanced Subtitles (no update needed, still working)
Native Ultrawide Menus - SFSE (updated for 1.15.216)
Starfield 21x9 Ultrawide Fix LoadingScreens (newly released for 1.15.216)
PerkPointsPerLevel (NOT compatible with 1.15.216; needs update)
Player Eyes Stuck at the Dialogue Target Bug Fix - SFSE (updated for 1.15.216)
So if this mod (BAE) is not working for you, then there is something causing an error/conflict on your end. You may have a mod that needs to get updated for 1.15.216, which may be causing errors/conflicts. Be advised, due to the new 1.15.216 having made a lot of changes in the coding (from what I've read), almost (if not all) DLL-based mods (aka any/all mods that list SFSE as a Requirement) have been broken and will need to get updated for 1.15.216.
"Creations are currently loaded. Note: Achievements are disabled."
Nothing disrespectful in asking for re-confirmation from author or from fellow gamers. We are all aware that this patch was a bit more impactful on SFSE, etc., as stated by Ian.
The intention was to make the mod more resilient by reducing the scope so that there's less of a chance for something to break between updates. Joke's on me, we had 1.14.74 for 6 months before the next update, so that didn't really matter- though it did help when 1.15.216 broke everything.
As far as I'm aware, you should only see the achievements warning when loading a save the first time you load a save game that was made without mods/a previous version of the mod, and after that it shouldn't pop up again, which I think is fine. The mod does continue to remove the popup when the console is opened, as well as the [C] tag on individual saves, which is the canary that lets you know it is working.
And yes, there are no [C] tag present/showing in the save file names, hella nice. :)
When I say "that was intentional", this is part of what I mean.
When Starfield launched, the game worked similarly to other recent BGS games, in that the "modded save" flag really only affected the display name in the menu, and the AddAchievement function.
When Creations launched this changed and Starfield now uses the flag for some actual game logic while loading saves. I don't want to mess with that aspect of the game, and the actual point of this mod (Enabling Achievements) doesn't require this, so I think it's safer not to. This does mean that with the flag the Player ID of saves does change and they're in the separate (Creations) list. I don't want to separately try and mess with that aspect of the game either because I don't want the mod to cause any issues when it comes to creating new saves- making the game think it can't save, or overriding saves when it's not supposed to.
I don't know if anyone can help me, but I've suddenly found upon updating that my existing saves are now being flagged with "Creations are present, achievements disabled" warning which I've never had with this mod.
Has this happened to anyone else since updating etc?
Edit 29.05 PM - I've loaded my existing saves and the usual creations warning came up in the main menu. I saved a new game & my game save was flagged with [C] for creations. However! I trialed an easy achievement and it still worked fine, so the mod works even though it gives warnings etc :)
Though in my previous times using this mod, I never had this warning... so I kinda want somebody else to confirm this is supposed to happen too.
@Vladimir: are you absolutely sure that it's not working? Or that's just an hypothesis?
Behavior is, prompted that achievements will be disabled, and then when I test saving it after loading, the game did in fact create a new "character" that had that modded thing after its name. Presumably that means it's not working correctly.
"...However! I trialed an easy achievement and it still worked fine, so the mod works even though it gives warnings etc :)..."
Aren't achievements per account and across characters? I've completed 90%+ achievements and don't want to risk the last 10%.
I loaded my usual save and used the console command to give me the weapons and mats, and went through modding all of the weapons until the achievement popped up/showed on my Steam page.
I installed the latest Baka Achievement enabler and when I load my game I still get the notification about the
achievement. Is that normal? I'm currently on the last version of the game.
At this point looks like Starfield is entering Skyrim territory where staying on a specific version is preferable to updating.
Need the version of this mod that works with the previous version, where all things SFSE still worked.
Does anyone know if it still allows the achievements despite the message?
Interestingly it did get get rid of all the [C] that was on the saves, so maybe it still works?
I have updated my SFSE, the Address Library and this mod, but when I go to load my game, I get the "Creations are loaded. Note: Achievements are disabled" message. I installed it via ModManager, which was how I always did before, then uninstalled it and reinstalled manually (yes to the same folder the Starfield.exe app is in) and same result. What am I doing wrong?