-
Notifications
You must be signed in to change notification settings - Fork 102
feat: new Voice chat event, fixes for Exiled events that use LabAPI, and additions to Event and Event<T> #730
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
base: dev
Are you sure you want to change the base?
Conversation
Fix item owner being done in the wrong order Revert "Fix item owner being done in the wrong order" This reverts commit e8cfd54. Update VoiceChatting.cs Update and rename VoiceChattingEventArgs.cs to SendingVoiceMessageEventArgs.cs Create ReceivingVoiceMessageEventArgs.cs Update Player.cs Update and rename ChangingSpeakerStatusAndVoiceChatting.cs to ChangingSpeakerStatus.cs Delete EXILED/Exiled.Events/EventArgs/Player/TransmittingEventArgs.cs Update Player.cs Create TransmittingEventArgs.cs Update Player.cs Update Player.cs Update Player.cs Update Player.cs Create VoiceChattingEventArgs.cs Update TransmittingEventArgs.cs Update Player.cs Update ReceivingVoiceMessageEventArgs.cs Update SendingVoiceMessageEventArgs.cs Update SendingVoiceMessageEventArgs.cs Update Player.cs Update Events.cs Update VoiceChatting.cs Update VoiceChatting.cs Update VoiceChatting.cs Update SendingVoiceMessageEventArgs.cs Update TransmittingEventArgs.cs Reverted braking changes deleted useless . doc checked its working /
…ther high-frequency events. This prevents EventArgs instantiation when no plugins are listening, significantly reducing GC pressure.
Update IPoolableEvent.cs
This reverts commit dafe934.
Someone-193
left a comment
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.
Good PR all around, the ctor changes arent breaking imo so I'm good with them. You should rename the PR to indicate the misc changes you added (fixes for Exiled events that use LabAPI and the Patched bool for Event, which you should also implement for Event while you're making that change)
Description
Describe the changes
What is the current behavior? (You can also link to an open issue here)
What is the new behavior? (if this is a feature change)
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Other information:
Types of changes
Submission checklist
Patches (if there are any changes related to Harmony patches)
Other