# Moving to Fish-Networking Moving to Fish-Networking will vary depending on which previous networking solution you are coming from. With other solutions changing their API so regularly it may be difficult to keep transition information up to date but we will try our best. If you encounter any questions we welcome you on our Discord, where our helpful community can get you started. {% embed url="" fullWidth="false" %} ## Leaving Mirror Networking More information will be added as it becomes available. {% hint style="warning" %} Always backup before making large changes. Having another copy of your project to reference during the upgrade is a great idea! {% endhint %} {% hint style="info" %} The majority of these changes can be done by using quick replace within your IDE! {% endhint %} **Mirror example conversion video:** {% embed url="" %} **Upgrade tool:** An upgrade tool is provided to help transition from Mirror to Fish-Net. The tool will replace several Mirror components with the like ones for Fish-Net. Note that while the components will be replaced the settings of your components will not be preserved. For best results keep a copy of your original project for reference until switching over. Currently supported components are: * NetworkIdentity * NetworkProximityChecker * NetworkTransform/Child * NetworkAnimator * NetworkSceneChecker Additional components from FirstGearGames Mirror Assets/Projects are supported: * FlexNetworkTransform/Child * FastProximityChecker * FlexNetworkAnimator * FlexSceneChecker {% hint style="info" %} The upgrade tool requires scripting defines to function. These defines should be removed after running the upgrade tool. MIRROR - for Mirror components. FGG\_ASSETS - for FirstGearGames assets. FGG\_PROJECTS - for FirstGearGames projects. {% endhint %} Before running the upgrade tool you will likely need to remove a few files. If using FirstGearGames Mirror assets or projects, delete any of the demo folders included for those assets and projects. In addition, any scripts requiring component NetworkIdentity will need to have the declaring line removed. ```csharp // Replace the following with an empty string. [RequireComponent(typeof(NetworkIdentity))] // The hotkey in Visual Studio is Ctrl + Shift + H. ``` **Component changes:** | Mirror | Fish-Networking | Notes | | ------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------- | | Interest Management |

ObserverManager
see also: NetworkObserver

| *Both support multiple conditions* | | NetworkIdentity | NetworkObject | | {% hint style="info" %} Changing out components can be a tedious task. Save time by using Window -> Fish-Networking -> Upgrading -> From Mirror -> Replace Components. This will swap out most components for you. Mirror and Fish-Networking must be within your project to run the operation mentioned. Afterwards you may remove Mirror. {% endhint %} **NetworkBehaviour property renames:** {% hint style="warning" %} Each IsServer, IsClient, etc option has two varieties: Initialized and Started. Initialized means the object has been marked as ready for network use by the side (eg: client or server). Started means the client or server socket is connected, but does not mean the object has been initialized for network use yet. When converting from Mirror you will most likely want to use Initialized. {% endhint %} | Mirror | Fish-Networking | Notes | | ------------------ | ----------------------- | --------------------------------------------- | | hasAuthority | IsOwner | *isLocalPlayer removed, use IsOwner instead.* | | isClient | IsClientInitialized | | | isClientOnly | IsClientOnlyInitialized | | | isServer | IsServerInitialized | | | isServerOnly | IsServerOnlyInitialized | | | connectionToClient | Owner | *Can be used on client.* | | connectionToServer | LocalConnection | | | netId | ObjectId | | **NetworkBehaviour callbacks:** callbacks such as OnStartClient for the most part are the same in Fish-Networking. Some of the callbacks do provide additional information which is not available within Mirror's callbacks. There are also several new callbacks to use. For a complete guide on using Fish-Networking callbacks click [here](https://fish-networking.gitbook.io/docs/manual/guides/network-behaviour-guides#callbacks). **Remote Procedure Call renames:** see [Remote Procedure Calls](/docs/guides/features/network-communication/remote-procedure-calls.md) for enhanced features and usage related to RPCs. | Mirror | Fish-Networking | Notes | | ------------ | --------------- | --------------------------------------------- | | \[Command] | \[ServerRpc] | | | \[TargetRpc] | \[TargetRpc] | *First parameter must be a NetworkConnection* | | \[ClientRpc] | \[ObserversRpc] | | {% hint style="info" %} RPCs within Fish-Networking has many advantages over Mirror; see [Remote Procedure Calls](/docs/guides/features/network-communication/remote-procedure-calls.md) for more information. {% endhint %} Mirror uses several singletons while Fish-Networking uses an anti-singleton design. There are still easy ways to access similar features. All of the same access can be returned from the NetworkObject component, as well by using [InstanceFinder](/docs/guides/features/instancefinder-guides.md). **Manager renames:** all of these may also be found within the NetworkManager. | Mirror | Fish-Networking | Notes | | -------------- | ---------------- | ----------------------- | | NetworkManager | NetworkManager | *Unchanged.* | | NetworkServer | ServerManager | | | NetworkClient | ClientManager | | | | TransportManager | *Fish-Networking only.* | | | TimeManager | *Fish-Networking only.* | | | SceneManager | *Fish-Networking only.* | **Switching from Mirror.NetworkManager:** the NetworkManager in Mirror features several overrides for state changes, such as when clients connect, disconnect, server start or stop, scene changes, and more. Fish-Networking instead uses sealed managers with events. To mimic the NetworkManager of Mirror create a new MonoBehaviour and place it on your NetworkManager object. Instead of using overrides subscribe to your needed events from each appropriate Fish-Networking manager. ```csharp // Mirror example. // Called when a remote client connects. public override OnServerConnect(NetworkConnectionToClient conn) {} // FishNet example. // Called when a remote client state changes. networkManager.ServerManager.OnRemoteConnectionState += YourCallback; ``` | Mirror | Fish-Networking | | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | |

ServerChangeScene

OnServerChangeScene

OnServerSceneChanged

ClientChangeScene

OnClientChangeScene

OnClientSceneChanged

|

SceneManager.OnLoadEnd

SceneManager.OnClientPresenceChangeEnd

See SceneManager guide for more information.

| | OnServerReady | SceneManager.OnClientLoadedStartScenes | |

OnServerConnect

OnServerDisconnect

| Servermanager.OnRemoteConnectionState | |

OnServerAddPlayer

OnClientNotReady

OnStartHost

OnStopHost

| Not needed. | |

OnStartServer

OnStopServer

OnServerError

| ServerManager.OnServerConnectionState | |

OnStartClient

OnStopClient

OnClientConnect

OnClientDisconnect

OnClientError

| ClientManager.OnClientConnectionState | ### Automatic online/offline scenes To mimic the Online and Offline scene setting in the Mirror NetworkManager you can add the [DefaultScene](/docs/fishnet-building-blocks/components/defaultscene.md) component to your network manager object and fill it in with your desired scenes. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://fish-networking.gitbook.io/docs/guides/upgrading-to-fish-net.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.