[Beta 2] UNet weaver error for virtual methods

In our project all UNet commands and RPCs (about 40 methods) are defined as empty virtual methods on base class NetworkPlayer and have implementation in derived classes: one for server project and two for client project (1st person and 3rd person players).

Now when opening the project in 2017.1.0b2 I get the following error which weren't there in the first beta:

Is this a breaking change or is this a bug?

 

@MichalBUnity I don't think that's true. In our project they worked perfectly fine at least since 5.3 up to 5.6 and 2017.1.0b1.

 

Code (CSharp):

1. public class Player : NetworkBehaviour
2. {
3.     ...
4. }
5.  
6. public abstract class NetworkPlayer : Player
7. {
8.     ...
9.     [Command] protected virtual void CmdSearchContent(string itemId, uint callbackId) { }
10.     [ClientRpc] protected virtual void RpcSetDamageCoeff(float damageCoefficient) { }
11.     ...
12. }
13.  
14.  
15. public class ServerPlayer : NetworkPlayer
16. {
17.     protected override void CmdSearchContent(string itemId, uint callbackId)
18.     {
19.         // server logic here
20.     }
21. }
22.  
23. public class ClientPlayer : Player
24. {
25.     protected override void RpcSetDamageCoeff(float damageCoefficient)
26.     {
27.         // 1st-person logic here
28.     }
29. }
30.  
31. public class ObservedPlayer : Player
32. {
33.     protected override void RpcSetDamageCoeff(float damageCoefficient)
34.     {
35.         // 3rd-person logic here
36.     }
37. }

Then we invoke them as usual:

Code (CSharp):

1.     // on client
2.     ...
3.     Player.CmdSearchContent(operation.Item.Id, confirmId);
4.     ...
5.  
6.     // on server
7.     ...
8.     RpcSetDamageCoeff(damageCoefficient);
9.     ...

 

No worries, I've got a separate branch for testing out beta versions. Just trying to detect and report any issues as soon as possible, before they seep into main release.

 

This seems to be fixed in the latest beta (b4). The project compiles fine now.