Skip to content

Index entry bug with no_fred flag in Props.tbl #7545

Description

@PremiumColt

When trying to spawn an object without the "no_fred" flag, it instead spawns an object that has the flag. For example:

Planet1, 2 and 3 have the flag
Asteroid1, 2 and 3 do not
(entries 1-20 are planets and all have the flag enabled, while 21-26 are asteroids that do not have it)

Asteroids will correctly appear in the drop-down select list, and planets are correctly hidden, but spawning Asteroid1 will spawn Planet1, Asteroid2 will spawn Planet2 etc

Removing the "no-fred" flags from all entries (the planets) will correctly spawn the appropriate object from the list.

Now the neat part. If I remove the flag from just the first planet entry, then when I spawn it it will spawn the planet correctly, but then when I spawn Asteroid1 it will spawn the second planet. Spawning Asteroid2 will spawn the third planet etc. What I think is happening is that spawning the first object in the list will instead try to spawn the first object in the table that has the flag.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions