This repository has been archived by the owner on Aug 15, 2022. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 305
Upgrading Forge Remastered to Develop branch or different version
TheYellowArchitect edited this page Apr 9, 2021
·
1 revision
For some reason, you may want to change branches. From master to develop, for example, for whatever reason.
But if you do it as expected, all your NCW (Network Controller Wizard) changes will be lost, RIP those RPCs you spent time on.
So, first of all, in case you fail some of the steps, save/backup your project (git ftw) Take the old generated folder, and move it away. Now, delete everything, or simply replace it with the new branch of Forge. Paste back the old generated folder. The NCW should work smoothly.
For changes in MultiplayerMenu and NetworkManager and so on, you can pretty much replace them :)
Getting Started
Network Contract Wizard (NCW)
Remote Procedure Calls (RPCs)
Unity Integration
Basic Network Samples
Scene Navigation
Master Server
Netcoding Design Patterns
Troubleshooting
Miscellaneous
-
Connection Cycle Events
-
Rewinding
-
Network Logging
-
Working with Multiple Sockets
-
Modify Master and Standalone servers
-
NAT Hole Punching
-
UDP LAN Discovery
-
Offline Mode
-
Ping Pong
-
Lobby System
-
Upgrading Forge Remastered to Develop branch or different version
-
Forge Networking Classic to Remastered Migration Guide
-
Script to easily use Forge Networking from sources
-
Run Two Unity Instances with Shared Assets for Easiest Dedicated Client Workflow