If a NetMulticast function is calledl, it will force non-relevant Actors to become relevant for a few seconds before going back to non-relevant.
RESULT:
Server will become relevant and Client will see server pawn for a few seconds, before server Pawn switches back to non-relevant.
EXPECTED:
Non relevant Actors don't change relevancy status on multicast calls.
Head over to the existing AnswerHub thread and let us know what's up.