-
Notifications
You must be signed in to change notification settings - Fork 148
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
Invisible Targets #1012
Invisible Targets #1012
Conversation
Did a simple |
Nope, that breaks it. But Pls merge Tinter#1 I noticed that the center of the target has to be outside the VIEW GEO LOD of the object the target is placed on. This sucks, because that means that you can only make things a target from one direction. Sideways the AI would miss. Pretty finicky, but better than nothing. Still no idea on how to fix the nametag, but at least the icon is pretty and totally not stolen from Google. |
move to ai component, icon, formatting
Team wants this in ACE instead, because out of scope for CBA. |
Should we discuss it here or not? |
Sure. |
Well without knowing the arguments, I'd say that this seems more like a tool than a feature or gameplay modification. I can't say the scope of CBA is particularly well-defined, as in "if your request has these three things, it fits CBA". I tried looking into it and all I could find mostly seemed to point to the scope including things that are useful for mod makers and mission makers, generally and not specifically. I would associate ACE more with gameplay overhaul and extra features that are meant to influence gameplay directly. By putting this in ACE rather than CBA, anything using this feature would have a dependency on ACE rather than CBA, which doesn't make much sense since it doesn't have much to do with ACE in itself. I will concede that I haven't seen any features of CBA using new models, so I guess it fits under some interpretation of 'content'. Is there anywhere I can see why the team would like it in ACE instead of CBA? |
Bump? |
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.
¯\_(ツ)_/¯
That is correct, not fitting simply because it's really content. But we took another discussion and I guess decided it fits just as well as something else we have (I forgot what). :) |
When merged this pull request will:
B_TargetSoldier
,O_TargetSoldier
andI_TargetSoldier
that have models that don't block projectiles,scope = 2;
and fixing duplicate hitpoints error.As discussed in Feature request: Modified invisible targets #1011
If anything needs to be changed to comply with the CBA standards, just let me know and I'll be happy to change it.