Condition Problem

[Stormhound]

Unity version:
Fish-Networking version: 3.5.7 Pro

Describe the bug
The client is observing the object even though it does not meet all the conditions. I tested it with MatchCondition and SceneCondition. Test SceneCondition was always met so I tested MatchCondition. I could still observe the scene object whether it was met or not. It could be a bug.

To Reproduce
Steps to reproduce the behavior:

1. Go to 'NetworkManager'
2. Click on 'ObserverManager'
   3.Add MatchCondition & SceneCondition
   4.Move client to another scene using Fishnet SceneManager so it can satisfy SceneCondition.
   5.Add Client to random MatchCondition and test it with ObserversRPC, then add Client to same MatchCondition as scene object and test it with ObserversRPC again.

Expected behavior
As far as I know both conditions are must met to observe object and send data using ObserversRPC.

[FirstGearGames]

What is the expected outcome on step 5?

MatchCondition is ignored for NON-OWNED NetworkObjects if they are not explicitly added to a match.
EG: If the client is in match 5 but the NON-OWNED NetworkObjects are not in a match the client will still see the NON-OWNED NetworkObjects.

If you add the NON-OWNED objects to a different match the client should no longer see them.

[Stormhound]

I didn't know the Non-owned behaviour of MatchCondition, so I thought it might be bug since one of the condition was not met and yet I can send an RPC. That's my bad then.

[FirstGearGames]

Connections may be the same for if not in a match but I can or validate at this time.

…

On Sat, Apr 15, 2023, 10:49 AM Orçun Sarı ***@***.***> wrote: I didn't know the Non-owned behaviour of MatchCondition, so I thought it might be bug since one of the condition was not met and yet I can send an RPC. That's my bad then. — Reply to this email directly, view it on GitHub <#315 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGPJC3UJBZMN76JZTSUHYWTXBKYOVANCNFSM6AAAAAAWPRAXNA> . You are receiving this because you commented.Message ID: ***@***.***>