I haven't removed any lines... not that I know of, anyway. I've added my strings and entities onto the ends of both related files, and inserted the appropriate code for the GalaxyScenarioDef rather than removing anything (which I didn't need to do anyway).

I thought that it might be some obscure like that but I don't recall having ever actually deleted lines...

I was just about to critique your entire post and tell you what you may have skipped. Judging from the error, you probably didn't skip anything, but rather forgot to include things you did do in your post.

The error indicates you forgot to add something to your files.

renderShield TRUE

This line should be between these two. . . like this.

ShieldMeshName "Shield_PhaseBattleship"

renderShield TRUE

maxAccelerationLinear 100.000000

Here is how to interpret your particular error message. It may come in handy in the future.

Text FileArchive missing Label. The game knows precisely the problem, but it isn't going to fix it for you.

File: C:\Users\Botemaster\AppData\Local\Ironclad Games\Sins of a Solar Empire\Mods-Entrenchment v1.041\In The Admiral's Service\GameInfo\CAPITALSHIP_PHASEBATTLESHIP.entity The game is telling you precisely which file contains the error
Label: renderShield The game is telling you what is missing
Line Number:237 at this line
Line Contents:maxAccelerationLinear 100.000000 and this is what is here instead.

The repetition of the error is because it skips to the next line looking for the missing information. If it ever did find it, it would then look for maxAccelerationLinear until it reaches the end. This is why everything must be in proper order.

My conclusion is that the file for your ship (and possible all your ships, but only the ones you added from Forge Tools) is very old. You probably took them directly from forge tools, and forge tools directories have not been updated for some time.

My suggestion is that you visit this link: https://forums.sinsofasolarempire.com/353296

If a new version of your preferred type of sins is released, here is what you do. Take the new conversion file from the Sins Main Directory (ie: ConvertData_Diplomacy). Paste it in the GUI converter directory. Rename it to the new version of your preferred sins (ie: ConvertData_Diplomacy.95, this is Beta 3 which has not had its ConvertData updated into the GUI). Then copy and paste, for this example, the Diplomacy folder (which is in the Sins main directory) into the "Mods-Diplomacy v0.95" folder, which is the directory for the latest version of Diplomacy, appropriate for this example. 

Check your download directory to see if you already have the appropriate converdata you desire. It recognizes which to use based on which version of mod directory you have (based off the directory's name, I think, not sure.) Anyways, that's how it's worked for me.

You'll now have all the appropriate files with no errors, up to date, to mod at your own whims. I personally make the entire files from scratch.

This game includes a few new lines or less in some updates for a group of similar entity files, or any other sort of files. When the game updates, copy/paste your mod into the new directory, and you should eventually be able to interpret what the error popups mean and update all your files in less than 30 minutes.

That particular addition occurred a while ago. Perhaps you unknowingly recently updated your game. The renderShield code was added sometime around late Summer. Most things, even things without shields, make this value as TRUE. Rarely is it FALSE. The latest Forge Tools came from before this line was added.

Oh, and make sure you actually run the program, after having done all that copy/pastya/rename stuff. Select the mod folder.

I am not sure how you would run without the renderShield TRUE in any ship entity file for so long. The game either chose to ignore your ship entity for some reason, or you only recently unknowingly updated.

Did you have the ship added to a race before making the new race? I think when it loads that it only checks those frigates that is registered in one of the race files. An example is that if you have an ability that refers to a buff that doesn't excist it won't say anything when loading the mod. Then if you hover your cusor over the ability ingame you will get an error telling you that it couldn't find the buff and then minidump.

gruntmaster -

Until I added the Vallus, all of my previous ships were just replacing vanilla ones.

Aractain -

Something about verticies overlapping on triangles or something. I suspect it's from a few of the extrudes and can possibly be welded. Some of the errors were also related to the weapon pivots which I fixed manually - porting from 3ds max to XSI really screws with the pivots (and the tangents as well, it smooths the crap out of the model and when we try to fix it we get a bunch of strange white lines appearing on edges, and my friend doesn't really know anything about XSI so fixing these problems is very difficult).

We have ironed out most of the errors. Some were from ngons.

Now we're just having weird problems with one of my ships having strange holes in it for some reason.

Also, tangents. Dear God tangents. They either smooth out the model to crap or you can play with them and fix the smoothing but then they make a ton of these weird lines.

Yeah, we're not really liking XSI.

argh lines

But hey, I've got a ton of sound effects made already and a portion of my sound track figured out, as well as a ton of custom particles, some with my own textures, some with Bailknight's. If there's anything I'm good at with this game it's making glowy explodey stuff.

Unfortunately, Particle Forge has a habit of doing this;

and there is NO WAY TO GET THE WINDOWS OUT OF THE TOP AAAAAAARGH man I've tried everything from changing resolutions to moving with keys to flailing around and screaming while bathing myself in the blood of a million virgins. Those windows just don't want to get out of their perch up there.

Im seriosuly confused about those white dots myself, I saw a refrence to them being a driver issue once? They arn't something wrong with the model though (as far as I can tell).

Its an anti-alising artifact.

Yeap I am serious, both about the solution and that it took days for me to "solve" it myself