Tutorial 1 Part 3 - DotNET

Technical terms used in this tutorial can be found in the glossary.

This tutorial shows:

• How to share values used in the object classes to the replicas of objects.
  

Share values

Edit "_RO_Player.rol" to be:

object Player { datablock NData; networking { NData(mPlayerColour) { Reliable; } }; }

Build the project. This time the "_RO_Player.cpp" will contain code to tell ReplicaNet to transmit the changes to the "mPlayerColour" variable. One C++ compiler problem you might see while building is "Skipping... (no relevant changes detected)". This means the C++ compiler doesn't think the file has changed but if it is a compiled ROL output file then sometimes it misses important code changes. It is a good idea to force a compile by choosing to rebuild all the project when this happens.

When you run two copies of this tutorial you should see in the output:

New Frame Object session id 0 and id 0 with type 0 Player::Tick(8.520287) mPlayerColour = 41 Object session id 0 and id 1 with type 1 Enemy::Tick(8.520411) Object session id 0 and id 2 with type 1 Enemy::Tick(8.520555) Object session id 0 and id 3 with type 1 Enemy::Tick(8.520668) Object session id 0 and id 4 with type 1 Enemy::Tick(8.520754) Object session id 1 and id 0 with type 0 Player::Tick(8.520856) mPlayerColour = 45 Object session id 1 and id 1 with type 1 Enemy::Tick(8.520967) Object session id 1 and id 2 with type 1 Enemy::Tick(8.521069) Object session id 1 and id 3 with type 1 Enemy::Tick(8.521152) Object session id 1 and id 4 with type 1 Enemy::Tick(8.521232)

This shows the "mPlayerColour" variable is now being transmitted automatically by ReplicaNet.

ReplicaNet can also be used to automatically update other types of variables such as position, speed or any other values.

This concludes tutorial 1.