-
Notifications
You must be signed in to change notification settings - Fork 81
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
MarkerVision: A Bomb Radar Rework #1203
Conversation
I probably have to handle players being added to / removed from the team as well |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not a full review yet, IMHO this should be a draft.
i wanted to Veto calling this bombvision
or radarvision
.
Neither of them properly reflect what exactly this is and it is confusing as hell. Even more so as both names are still used throughout the PR.
Naming a library after a builtin item (that does not even use this) is beyond confusing.
The name for this i know from other games would be along the lines of "POI hints" (POI = Point of Interest) maybe we can find a better descriptive word even, but naming this after a specific item/equipment is out of the question for me.
I don't get why this should be a draft as I'm more or less done with this |
"Even more so as both names are still used throughout the PR." -> the PR itself does not refer to its introduced library in a consistent way which seems to be because of a recent change which in turn means it's still actively worked on -> should be a draft |
fwiw i think POI / InterestPoint would be a decent name for it |
Seconding. While I think radarvision is a better name than bombvision, it can still be confused with the radar item that is completely unrelated to this HUD feature. HUD Markers might be a better name? |
Is there any input on this PR? |
Sorry i'll probably review it this weekend. Until then i'll try one last time to propose another name. If that doesn't find support i'll just shut up about it. Firstly i'll try to explain why i don't particularly like
My proposal therefore would be either waypoint or signpost.
|
How about ("entesp" = entity + esp)? |
We don't want to use abbreviations, but thanks for the suggestion! |
What about |
We already have a marks module |
Maybe integrate it into the marks module? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Besides the name, the code looks fine. I also dont have a better idea. 😄
nah, this has nothing to to with the marks module. The marks module just adds a colored stencil that is rendered on top, this adds networking, role change tracking, death tracking, icons, text and much more. Imho, they are not related |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
a few doc suggestions and a small nit. Otherwise looks good
Added a new markerVision system that is similar to targetID. It handles wallhack and UI. It supports teamchange as well
https://www.youtube.com/watch?v=hdo0waT3cOw