Well, usually if you want help, you have to wait until someone decides to offer it which can sometimes be a day or more, posting again after an hour and some change isn't going to speed anything up, just make people think you're being rude and demanding when none of us are under any obligation to help what so ever...  This should also be posted in the modding section since it clearly deals with modding.  Also typing in large capital letters isn't helping you out at all either...  Just saying.

Now to answer your problem.

If you're creating a whole new ship, it's not showing up in the frigate factory because you haven't added your modified scout to the player(faction).entity file.  Look for the frigate info section, add one to the count and add in a line for your modified scout. Or it's not showing up because you haven't added the entities to the entity manifest.  Or both.

If all you've done is modify the existing ship and it no longer appears, that would be because you changed the name of the ship entity file and you need to change it back.

A ship entity can point to a mesh and texture for another ship and use them.  There's nothing preventing this.

Because you didn't do something correctly.  Without an error message to refer to, you can't be pointed in the right direction.

You should be using the developer exe to play the game when modding.  That way you will get error messages before the game crashes and dumps.  It'll also create a log file for you to refer back to.  In your Sins game folder, you will find the dev.exe  Play the game with that.

It's called a dump file not a dumb file, and again, without telling me what error message comes up, all I can say is yes, you made a mistake, but I can't point you in the right direction.

Sounds like it's referencing a mesh that doesn't exist.  Like I said before, play the game using the dev exe.  That way you will get error messages that pop up while you play and before it crashes.  Those error messages will point you in the right direction on what is broken and why you're crashing.

I have used the Dev and this Error Panel appears:

Error #1

Text FileArchive missing Label.

File: C:\Users\Multimedia\AppData\Local\Ironclad Games\Sins of a Solar Empire\Mods-Diplomacy v1.01\Limited Modifications\Window\MainMenuScreen.window
Label: updateProcessCommandLine
Line Number:73
Line Contents:sinsButton

Error #2

Text FileArchive missing Label.

File: C:\Users\Multimedia\AppData\Local\Ironclad Games\Sins of a Solar Empire\Mods-Diplomacy v1.01\Limited Modifications\Window\MainMenuScreen.window
Label: entrenchmentProcessCommandLine
Line Number:74
Line Contents:sinsButton

 Error #3

Missing \n in C:\Users\National Security\AppData\Local\Ironclad Games\Sins of a Solar Empire\Mods-Diplomacy v1.01\Limited Modifications\.\entity.manifest

This is a mostly harmless error message usually caused by forgetting to hit enter at the end of an archive file.
It is only here to verify that the buffer given to read the string is big enough to hold the string read from the file.
If there is no \n character then this particular bug can't be properly detected.

to fix - put a newline at the end of this file.

//That is all errors found recently during the Intros

Nope I am not updated, however I am cautious about the balanced of my mods to the new updates.

Anyway, I managed to fix those 3 but this Assert Panel appears after my modified ScoutShipDoom finishing constructions in Factory.

Here is the Assert Panel says:

Assert @ c:\projects\Perforce\SinsDiplomacy\main\CodeSource\GS/Entity/Interfaces/IAbility.cpp(826)

m_owner->GetIStarBasePtr() != NULL

I tried to Navigate within that file but it seems that the path never exists.

The ability you're using, I assume you copied the AbilitySelfDestruct.entity is looking for the star base upgrade to see how powerful it should be.

In it you should see the lines:

maxNumLevels 2
levelSourceType "StarBaseUpgradeLevel"
sourcePropertyType "AbilityBLevel"

Change the max levels to 1, the source to FixedLevel0 and remove the property type.

You should make it show something like this:

isUltimateAbility FALSE
maxNumLevels 1
levelSourceType "FixedLevel0"
aiUseTime "OnlyWhenAboutToDie"
aiUseTargetCondition "Any"

That should get rid of the assert.