[SOLVED] cl_ghost_items blues

yo yo yo

some comments regarding cl_ghost_items and cl_ghost_items_color

we like playing with ghost items off, and we can't figure out a way to hide them completely. setting cl_ghost_items to 0 makes them gray. setting cl_ghost_items to -1 or 0.0001 does make most ghosts disappear (we are assuming they do not hide perfectly, but become too faint to see), but this one health pack appears to be glitching (see attached screens: first active item, then ghost item)

You need to set cl_ghost_items_color to "0 0 0" for them to be completely invisible.

we can confirm setting cl_ghost_items_color to "0 0 0" also works to make ghost items invisible, except for this one type of healthpack, shown. we think it may be an issue with its model.

we can confirm setting cl_ghost_items_color to "0 0 0" also works to make ghost items invisible, except for this one type of healthpack, shown. we think it may be an issue with its model.

Can you report that either in the bug forum or the issue tracker? https://gitlab.com/xonotic/xonotic-data.pk3dir/issues

This has been fixed in latest Git master, and will be in the next release.

This has been fixed in latest Git master, and will be in the next release.

Nice.
Is that going to be a whole year until then?

This has been fixed in latest Git master, and will be in the next release.

we can confirm today's git seems to address the healthpack issue, as well as the scoreboard regression with overlapping color tags

Antares*, this bug is not exactly a show-stopper it's more of a minor annoyance not even detectable by people with default ghost item settings.

This has been fixed in latest Git master, and will be in the next release.

we can confirm today's git seems to address the healthpack issue, as well as the scoreboard regression with overlapping color tags

Antares*, this bug is not exactly a show-stopper it's more of a minor annoyance not even detectable by people with default ghost item settings.

It's not.
That post is my poke at the pace of development.

Which before someone takes offense, and starts finger waving about contributing code and whatnot, is intended to be a joke.

If you were trying to poke at the pace of development, a more apt target would be the number of commits hitting master rather than the infrequent releases. We've never had any issues with the former. With autobuilds even the latter isn't too bad.

No, Antares, bad! You can't have fun on a video game forum.

Are you guys going to release Xonotic 9, 18 or 36 years later?

You can always join the effort and help.