-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Tweaks for the holopad #33928
Tweaks for the holopad #33928
Conversation
I think you should be able to change the listening radius of a holopad in game up to a certain point. |
|
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
Yeah, there could be some additional controls on the 'in-call' screen to toggle a conference mode (which has a wider listening range) as well as a mute toggle. That would have to wait 'til later though
The name + label was to replicate how hand held radios handle relayed message but I see your point, I'll think on it. Having the name of the holopad the caller is coming from is a good idea. Might also have to wait on this one |
Oh also, its not really needed after all (since the amount of holopads doesnt seem to be an issue) but I still think a search field would be cool |
Thats good to know but I'll keep the filter in mind for the furture |
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.
I noticed don't know enough about this system yet to give it a proper review.
But at least some cleanup :)
Co-authored-by: slarticodefast <161409025+slarticodefast@users.noreply.github.com>
Co-authored-by: slarticodefast <161409025+slarticodefast@users.noreply.github.com>
Since it's a brand new system, you know as much as everyone else! :D |
Summoning @SlamBamActionman so we can get it into the next release in time. |
About the PR
A collection of minor tweaks and bug fixes for the holopad before it gets merged into stable
Why / Balance
This PR changes the following:
Technical details
N/A
Media
N/A
Requirements
Breaking changes
Just in case someone is using this code already...
Entities using the telephone system/component now handle transmission ranges differently
Firstly,
TelephoneRange.Long
has been removed; any instances should be replaced withTelephoneRange.Map
Secondly, additional options for configuring which telephones can contact other telephones -
CompatibleRanges
(List<TelephoneRange>
) andIgnoreTelephonesOnSameGrid
(bool
)Where
TransmissionRange
determines which telephones are in range of a source,CompatibleRanges
is the whitelist that determines which of these it can initiate a call with (based on the receivers' ownTransmissionRange
). For example, long-range holopads have aTransmissionRange
ofTelephoneRange.Map
, so they can potentially contact any other holopads on the map. However, they haveCompatibleRanges
ofTelephoneRange.Map
andTelephoneRange.Unlimited
, so they can only connect to other holopads that have aTransmissionRange
ofTelephoneRange.Map
orTelephoneRange.Unlimited
(e.g., other long-range and quantum entangling holopads)IgnoreTelephonesOnSameGrid
, on the other hand, when set to true, will prevent telephones from contacting any other telephones on the same grid. This bool will be ignored if the telephone has aTransmissionRange
ofTelephoneRange.Grid
Changelog
N/A