#1 Open Source Unity Networking Library
Go to file
vis2k 00a1004b41
Weaver sourcebased hlapi2019.2package (#587)
* move weaver into assets folder

* disable tests for now

* asmdef

* add logs

* Use UNET's WeaverRunner code, slightly modified to find Mirror assembly

* Use UNET's 2019.2 package Weave function changes

* compiler messages error checked moved into separate function

* fix typo

* syntax

* replace 'var'

* rename

* replace var

* fix log

* update comment

* syntax

* rename to assemblyPath. no need for an extra variable.

* remove extra variable

* fix typo

* remove old code

* don't use .Contains to find Mirror dll. that's crazy. would fail for all DLLs in Mirror folder.

* look for 'this' assembly separately

* separate unityEngine assembly search

* add comment

* move null check up

* move null check upwards

* move outputDirectory down

* check process result properly

* use our previous way to find unity engine dll

* rename to unityEngineCoreModuleDLL again

* improve output directory construction

* move unityengine dll finding upwards

* move foundThisAssembly down, where it is used

* add comments

* split dependency code into separate functions

* add TODO

* store this assembly in a variable

* split dependency search depending on if we found assembly or not

* move usesMirror logic into if and out of 'not found' else

* syntax

* improve order

* GetNonDynamicAssemblyDirectories helper function

* check File.Exists instead of exception

* improve comment

* rename HlapiRuntimeAssemblyName to MirrorAssemblyName

* reuse MirrorAssemblyName

* remove telepathy check

* rename to MirrorRuntimeAssemblyName

* add MirrorWeaverAssemblyName

* reuse name consts

* don't use contains to check if assembly depends on Mirror

* add actions for testing again

* make CompilationFinishedHook public so it can be used by tests

* fix typo

* Mirror.Tests.asmdef references weaver asmdef

* reenable tests

* pass error handlers to Weaver Processing for tests to work
2019-03-13 12:17:04 +01:00
.github/ISSUE_TEMPLATE update branch suggestions 2019-01-18 08:57:02 -06:00
Assets Weaver sourcebased hlapi2019.2package (#587) 2019-03-13 12:17:04 +01:00
docs Better grammar and typos 2019-03-11 18:23:42 -05:00
ProjectSettings 2018.3 ProjectSettings detected too late 2019-02-25 20:42:58 +01:00
.editorconfig Switched braces to silent as suggested by Petris 2019-02-23 07:32:17 -06:00
.gitattributes ensure future c# code has consistent EOL 2019-01-05 10:09:05 -06:00
.gitignore We don't need to commit mdb files 2019-02-07 17:48:02 -06:00
appveyor.yml Source based instead of dll (#277) 2019-01-13 21:08:54 +01:00
CONTRIBUTING.md Add empty class bodies to code convention 2019-02-28 12:16:19 +01:00
LICENSE License updated 2018-08-24 17:01:31 +02:00
README.md Appveyor cannot run tests in source based mirror 2019-03-10 12:50:32 -05:00

Mirror Logo

Download Documentation Forum donate Build status Discord release

Mirror is a high level Networking API for Unity, built on top of the low level Telepathy library.

Mirror is built and tested for MMO Scale Networking by the developers of uMMORPG, uSurvival and Cubica.

Mirror is optimized for ease of use and probability of success. Projects that use Mirror are small, concise and maintainable. uMMORPG was possible with <6000 lines of code. We needed a networking library that allows us to launch our games, period.

With Mirror, the Server & Client are ONE project (hence the name). Instead of having one code base for the server and one for the client, we simply use the same code for both of them.

  • [Server] / [Client] tags can be used for the server-only and client-only parts.
  • [Command] are used for Client->Server, and [ClientRpc] / [TargetRpc] for Server->Client communication.
  • [SyncVar]s and SyncLists are used to automatically synchronize state.

What previously required 10.000 lines of code, now takes 1.000 lines of code. Therein lies the magic of Mirror.

Note: Mirror is based on Unity's abandoned UNET Networking system. We fixed it up and pushed it to MMO Scale.

Documentation

Check out our Documentation.

The main difference is that you have to use using Mirror; instead of using UnityEngine.Networking; at the top of your scripts.

Oh, and you won't have to worry about channels, low level networking, packet loss, lack of support or bugs ever again. Mirror just works.

Usage Guide

If you are coming from a current UNET implementation or are seeking the stable version:

Import mirror from the Asset Store into your project.

Alternatively, you can install new releases manually:

Note: New releases are bleeding edge and may come with undiscovered bugs. Use at your own risk!

  1. Download Mirror (for Unity 2018.2.20 or 2018.3.x).
  2. Decompress the zip file in Assets

Migration Guide

If you are still using UNET and want to switch to Mirror, you should check out our Migration Guide. Don't panic, it's very easy and won't take more than 5 minutes.

Example Projects

Download Mirror from the Asset Store, we have several small example projects included.

For a fully polished complete project example, consider uMMORPG or uSurvival.

Community Transports

If you don't want to use Telepathy or UNET's LLAPI as low level transport, then check out:

Donations

Mirror is developed by volunteers. If you like what we are doing, consider leaving a small donation.

Benchmarks

Contributing

If you would like to contribute, feel free to submit pull requests and visit our Discord Server.

We follow the KISS principle, so make sure that your Pull Requests contain no magic.

We need Mirror to be MMO Scale. Bug fixes are always highly appreciated. New features will be considered very carefully.