Base mob prototypes shouldn't create ghost roles.

[gradientvera]

Description

Example: MobDragon currently has the GhostTakeoverAvailable component on by default. This shouldn't be the case. There should be an inheriting prototype (e.g. MogDragonGhostRole) with the component instead. This way, you can choose whether to spawn a ghost role mob or not.

Anyway, I thought of this because I spawned a dragon on lizard in the admin testing area and a player took over it without me noticing.

[OctoRocket]

I would think that you would usually spawn in a dragon as an event so it already having a ghost role is preferable.

[EmoGarbage404]

I would think that you would usually spawn in a dragon as an event so it already having a ghost role is preferable.

doesn't mean you can't just have multiple prototypes, one with and one without. It's not a complete binary.

[mirrorcult]

I would think that you would usually spawn in a dragon as an event so it already having a ghost role is preferable.

There should be an inheriting prototype (e.g. MogDragonGhostRole) with the component instead. This way, you can choose whether to spawn a ghost role mob or not.

[Injazz]

That's a lot of prototypes, are you sure? For example there are 3 mice variants which means there should be 3 more with ghost role enabled

[Zylofan]

I think two people have started on this then stopped? Is this still needed?

If it is, is the solution to add a non ghost role version of each entity to the spawn list, or is the solution to just make all entities non ghost roles by default, and have the admin make them ghost roles once spawned?