Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

“pos_target” entity needs “target_name” field but “target_name” is deprecated and replacement “name” is not recognized #772

Open
illwieckz opened this issue Jul 18, 2015 · 4 comments

Comments

@illwieckz
Copy link
Member

Hi, this is an entity example stolen from the work-in-progress freeway map by @JacksonTech:

// entity 65
{
"classname" "pos_target"
"origin" "7760.000000 -1204.000000 96.000000"
"targetname" "pos_target2"
}

If I run the map with this entity as-is, Unvanquished says:

Warning: Entity #65 contains deprecated field targetname — use name instead

But if I replace the deprecated targetname keyword with the recommended name keyword as requested:

// entity 65
{
"classname" "pos_target"
"origin" "7760.000000 -1204.000000 96.000000"
"name" "pos_target2"
}

This name keyword is not recognized, Unvanquished says:

Warning: Entity (pos_target|#65) needs a name, so other entities can target it — Removing it.

It means #664 can't be fixed yet since up-to-date entity code is broken.

@illwieckz illwieckz changed the title “post_target” entity needs “target_name” field but “target_name” is deprecated and replacement “name” is not recognized “pos_target” entity needs “target_name” field but “target_name” is deprecated and replacement “name” is not recognized Jul 18, 2015
@t4im t4im self-assigned this Nov 24, 2018
@bmorel bmorel added the S-Old-Needs-Check This bug is old, let's check that it is still true label Oct 29, 2021
@bmorel
Copy link
Contributor

bmorel commented Oct 29, 2021

Not sure if adding a label adds a GH notification, so dropping a comment just in case it does not: is it still true?

@illwieckz
Copy link
Member Author

I doubt anything has been done.

@bmorel
Copy link
Contributor

bmorel commented Oct 30, 2021

Problem is, the issues are not really easy to track nor updated often. Those days, I closed more than a handful of old ones (originally, there were more than 305, we are at 290 now, and few were added since I did the 1st cleanup), so I'm checking when I'm a bit bored.

@bmorel bmorel removed the S-Old-Needs-Check This bug is old, let's check that it is still true label Jul 16, 2022
@bmorel
Copy link
Contributor

bmorel commented Jul 16, 2022

I believe it's related to #1850 somehow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants