I already answered you in the comments, try those steps and reply here with the log if those steps don't work.

well i cant update my SE because it is already updated. i can however delete SE and redownload but that takes ages with my connection and rather not do that.

and i dont know how to find the log of SE

Unsubscribing (if game is closed) will trigger an update, because that's where steam lists workshop updates too.
You have to wait for that so steam deletes the mod folder, before redownloading the mod by re-subbing (or just loading a world with the mod).

SE log is in %appdata%/SpaceEngineers/SpaceEngineers_<Date>_<Time>.log ... the date/time are going to be numbers, just telling you what they are because they don't look like date/time when you look at the file names xD

Subbed to this ages ago, never got it to work.
Today i deleted the \\.\\514062285.sbm_BuildInfo folder. Unsubbed from the mod.
Then resubbed. After resubbing, steam has yet to ever recreate the folder. Anyone have any tips? I have done basically everything i can think of, short of uninstalling the game......
Restarting gaming
Restarting steam
Restarting computer
Deleteing all the storage folders
Making sure steam and game was closed prior to resubbing

That's the storage folder that gets created by the code when you load into a world with the mod, which proves that it did work at some point :P

Can you post the SE log from when you tried running the mod, it should have its compile errors, see my above message on how to get that.

Got this in the Log:
[09:50:55/47] ERROR: Error on aimed defId=MyObjectBuilder_Cockpit/DBSmallBlockFighterCockpit - ModMessageBase-SetMember: MemberEnum out of enumerable range 13 BI_SEOutlined
at UIFun.Messagesv2.ModMessageBase.SetMember(Int32 MemberEnum, Object Value)
at UIFun.Messagesv2.ModHUDMessage.SetMember(Int32 MemberEnum, Object Value)
at UIFun.FontTexture.SetMember(Object arg2, Int32 arg3, Object arg4)
at Draygo.API.HudAPIv2.MessageSet(Object BackingObject, Int32 Member, Object Value)
at Draygo.API.HudAPIv2.HUDMessage.set_Font(String value)
at Draygo.API.HudAPIv2.HUDMessage..ctor(StringBuilder Message, Vector2D Origin, Nullable`1 Offset, Int32 TimeToLive, Double Scale, Boolean HideHud, Boolean Shadowing, Nullable`1 ShadowColor, BlendTypeEnum Blend, String Font)
at Digi.BuildInfo.Systems.TextAPI.CreateHUDText(StringBuilder sb, Vector2D hudPos, Double scale, Boolean hideWithHud)
at Digi.BuildInfo.Systems.TextAPI.TextPackage..ctor(Int32 initialSBSize, Boolean useShadow, Nullable`1 backgroundTexture)
at Digi.BuildInfo.Features.TextGeneration.UpdateTextAPIvisuals(StringBuilder textSB, Vector2D textSize)
at Digi.BuildInfo.Features.TextGeneration.PostProcessText(MyDefinitionId id, Boolean useCache)
at Digi.BuildInfo.Features.TextGeneration.UpdateWithDef(MyCubeBlockDefinition def)

will link the file but seems to be the same error repeating through the entire thing

Just to note tho, i installed it via plugin loader

Oh, that sounds like the textAPI version you have downloaded is older...
Try the re-sub thing with that mod aswell: https://steamhost.cn/steamcommunity_com/workshop/filedetails/?id=758597413 (with the same steps)

This is assuming the plugin loader gets it from the workshop download folder and doesn't download it on its own... if it DOES download it itself then you'll need to ask the plugin author how to force it to update xD

Hi Digi,

I have found an issue since the automation's update affecting connectors with the version of Buildinfo that is in Enenra's AQD Quality of Life mod pack. Basically you don't get an option to lock or unlock your connectors. If I remove the mod pack and add this standalone version they are all fine, but thought I would give you both the heads-up. I have already posted a bug report to Enenra's mod pack workshop page.

It's not a different version, that mod adds this mod as a dependency which means this mod gets added to the world automatically.
The connector issue is most likely from a mod that adds terminal controls to connectors.

Okay thanks for the info, I will continue to swap out different mods from the pack to see which recreates the problem and then post feedback to Enenra and the mod author for the affecting mod