Custom messages are not processed when sending to oneself
See original GitHub issueDescribe the bug Custom messages are ignored on the host when the receiving ID is the host itself.
To Reproduce
- Start hosting.
- Register a custom message handler with a
Debug.Log("I expect to see this!");
- Send a custom message to
NetworkManager.Singleton.ServerClientId
.
Actual outcome The log message will not appear. The custom message from client ID 0 to client ID 0 (itself) was ignored.
Expected outcome Since the host is both a client and a server I expect it to process all custom messages. It makes testing with a single client & server in 1 window much easier.
Environment (please complete the following information):
- OS: Windows 10
- Unity Version: 2022.1.0b1.2470
- Netcode Version: v1.0.0-pre3
Issue Analytics
- State:
- Created 2 years ago
- Reactions:4
- Comments:5 (2 by maintainers)
Top Results From Across the Web
c++ - Is it possible to send a custom message ...
Sending either type to an application (like Tast Manager), that neither has its top-level window class documented, or its application-private ...
Read more >Custom message not working | XM Community
Hi I have a custom end of the survey message, however while doing tests i realized that the message i am getting at...
Read more >Can custom messages be located within a package?
Turns out it is very simple to use your custom message within the same package: Your custom message gets imported by default, so...
Read more >Creating and managing custom messages - DiSC Profile
If you're still concerned that your variables and edits won't show correctly, you can send the message to yourself. First, you can create...
Read more >Custom Messages
A brief explanation of Custom Messages use in Netcode for GameObjects (Netcode) covering Named and Unnamed messages.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This was fixed in #2296, and should be present in the upcoming 1.2.0 release.
Closing the issue as 1.2.0 has been released and the fixed is now live