General

Cat names with d

Cat names with d

Cat names with dashes) and have a single parent. Here's a list of the common names:

(As it stands, there's no support for naming babies in the database. I was just checking how it was being handled with the dashes: it was a strght copy/paste from another system.)

Edit: And, in case anyone is wondering, the name of the parent's ship is derived from their ship type and the name of their ship, and then a suffix that I didn't want to include. This is called a Ship Name, and the prefix is the first word of their ship name, and the suffix is a suffix they were using before their current ship name. For instance, Kess's mother's ship name was called "Invisimatter Kess" (first word is "invisimatter"), so her ship name is "Invisimatter Kess-Light". "Kess" is only the first word of the name, and the suffix is "-Light".

A:

This can be accomplished by changing the name of the child after the fact. If the parent and child ship are named Kess, then to change the name of the child, you would do the following:

Load the child ship.

Change the ship type.

Change the name of the ship.

Save the ship.

However, this is not possible for a child with multiple parents. If you have a parent ship named Kess, and the name of Kess's child is "Bella Goth", you cannot change Kess's name while also changing Bella Goth's name, because both are parents. So, one way to get around this is to name the child after both ships' names, like this: "Kess Bella Goth"

A more efficient way to accomplish this would be to have two separate ship types, one for each ship. Then, when you want to name a child, you can use both ship types. I'll be using the following ship types in this answer:

Parent Ship Kess: Type "Kess"

Kess's Child Ship: Type "Kess"

One problem with this approach is that when you save the ship, you will have two child ships that are named "Kess". And if you ever get another ship with that name, then you have to rename one of them or the name conflicts. You could solve this by using ship type "Kess 2" for both ships. However, you cannot have different ship types for children of the same parent ship.

A final solution is to have a ship that is the parent ship with a child that has no ship type, or name. It looks like you can have a mother ship with the same name as a child ship but no ship type, and it will accept ships named "Kess". In this case, your ship names would look like "Kess-Lite".

The mother ship (Kess-Lite): Type "Kess"

The child (Kess-Lite): Type not-set, name "Kess"

You can now name your ship Kess-Lite, and it will accept ships with the same name as long as they are not set to any type. Once you save, the ship will be named Kess-Lite, but it will still have the name "Kess". However, in this case, you will not have any duplicate names. You can then assign any type to the Kess-Lite ship.

The final solution is to use 2 names:

"Kess" for the actual ship type.

"Kess-Lite" for the ship's child.

There will only be one "Kess" ship, and the "Kess-Lite" ship can take the name "Kess".

Edit: This doesn't change whether the child will be able to accept ships of other types or not. For example, "Kess-Lite" can take the name "Kess" and will accept other ships. However, it will also take the name "Kess-Lite".

Kess-Lite (not-set) : Type "Kess"

Kess-Lite (Kess-Lite) : Type not-set, name "Kess"

Kess (Kess) : Type "Kess-Lite"

Kess-Lite (Kess-Lite) : Type "Kess"

A:

I tried with this structure, and I think it is the best solution:

type Kess as this type {

Name: string

}

type Kess_Lite as this type {

ParentName: string

}

type Kess_Lite_Ship_Type as this type {

Kess_Lite: this type

Name: string

}

And then:

// Kess_Lite

type Kess_Lite_Ship_Type as this type {

Kess_Lite: this type

Name: string

}

// Kess

type Kess_Ship_Type as this type {

Kess: this type

}

You can check that the names are the same by doing:

type Kess_Lite_Ship_Type as this type {

Kess_Lite: this type

Name: string

}

// Kess

type Kess_Ship_Type as this type {

Kess: this type

}

// Kess_Lite_Ship_Type

type Kess_Lite_Ship_Type as this type {

Kess_Lite: this type

Name: string

}

Of course, the first of these types is a Kess_Lite_Ship_Type. Kess_Lite is already defined so I don't need to repeat it. And I can repeat the type Kess_Lite_Ship_Type in a second or third way. So if you have three types that share a common field, this is very useful.