Well if you have a better way for me to get the errors+context then do tell.

I'll need more details on what block they equipped to cause that error.

It really isnt that important that our screen be filled with error text for blocks that are incompatible. No one would really notice if there just was no build info for something... Can't you just use a try/catch to ignore the error? If not, I can try to find out what causes it. One of my players has a ship that just constantly displays this error over it.

Try-catch is what shows the notification, if I didn't do that it would crash the game.
And I don't want to ignore exceptions, why would I do that... the point of that message is so I can be informed of it and fix it, then it will be gone, it's simple.

So far these are giving us the build info errors:
https://steamcommunity.com/sharedfiles/filedetails/?id=587688734 - Both seats
https://steamcommunity.com/sharedfiles/filedetails/?id=305329302 - Just the windows as far as I can tell I'll add more here as we get them.

Hmm, strange, I've added both of those mods along with equipping and placing the blocks you mentioned, and no errors from buildinfo at all, the block stats showed up fine too.

Can you post the entire mods list you're using, maybe something else is affecting those mods.

Open the world's Sandbox.sbc and post the contents of <Mods> tag, using pastebin.com or something, that'll allow me to add them quickly to a world :}

"Anti-Fighter Laser Turret" from https://steamcommunity.com/sharedfiles/filedetails/?id=1724382943

This is the collection I use on our servers: https://steamcommunity.com/sharedfiles/filedetails/?id=1715591667

Game doesn't support collections so I can't just add those mods to a world, doing it manually is too much of a chore, please send the mods list from the Sandbox.sbc in the world folder.

You can use the dependency system to make an empty mod (it needs to have at least a Data folder tho) that references all the mods you want to use, that'll effectively be a collection, but better since you can edit it via web and then just restart server to apply =)

Aah, I use Torch so it does parse and auto update by collection. Got another error from Kolt's Command pack.
Mods from sandbox.sbc - https://pastebin.com/3ZCB0pHu
Would you have time to maybe just use a config in Build Info's storage folder to allow hosts to disable the error display selectively? Or just print to console like every other mod.

Well I dunno what's going on then because I got zero errors on all those blocks equipped and placed with that mod list.
Does the error happen to you too or to only specific players?
Hmm, can you link me the server address so I can join and see if I get it too, because in SP so far I got nothing...

EDIT:
I did however find that holding a block still somehow selects placed blocks, that probably has something to do with it...

Steam is probably going to censor the server address, abundance.♥♥♥♥♥.me:27016 . Happens to everyone building non-vanilla and is common between that public and our private creative servers

Hmm that server downloads only 2 mods for me:

2019-05-28 12:06:04.177 - Thread: 1 -> List of used mods (2) - START
2019-05-28 12:06:04.178 - Thread: 1 -> Id = 1715591667, Filename = '1715591667.sbm', Name = '♥♥♥♥♥-SE Collection'
2019-05-28 12:06:04.178 - Thread: 1 -> Id = 1406994352, Filename = '1406994352.sbm', Name = 'TorchMod'

So I'm not sure what's going on.

It seems Torch actually automatically creates a mod linked collection as you mentioned earlier.

I too am receiving this error. Oddly however, it did not start until 30 minutes ago. I have not added or changed any of my mods in quite a few days. I am playing a personal game with 'friends' only. Not a server. I'm wondering if a mod I already had was auto updated in steam and it could be possibly clashing in that way ? But yeah, the notice keeps popping up about every 30 seconds or so across the entire screen, right in the middle, so that part is kinda getting annoying. :) oh, also, it seems to clear up if i plop down a vent. but starts up again on restart of game. so putting another vent down each time seems to help.

I've been noticing it happening to Vanilla blocks too lately, such as the small ship programmable block.

I really need some way of replicating it, maybe use some passive screen recording thing and when it happens look through the recording for what might've caused it... or just send the video I guess.

For now I've updated it to fix that cubebuilder selecting placed blocks, it's probably not it but who knows =)