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 instructions
pointcache edited this page Aug 17, 2017
·
5 revisions
Make sure you don'y use any of the prefabs in the FNR folder. If you're using NetworkManager, make a copy of it and put inside your own project folder. If you're using any MainMenu scenes, copy them and put them in your project folder. And make your project work off of those copies, not the originals, because they will be overwritten by upgrade.
Apparently in latest versions any usage of this file was removed and now the FNR editor works directly with .cs
and .meta
files of generated classes. This means this file is not required anymore for upgrading.
- Make sure you've read all the before upgrading.
- Commit your project, or if you don't use source control make a copy
-
Building FNR Build fnr, and make a
.unitypackage
- Open unity package and let it overwrite everything, make sure it doesn't overwrite your own Generated Files (in case of naming clash)
- open Wizard, open any class, hit
Save and compile
Should be good to go.
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