Newtonsoft Json For Unity
Nuget Unity3d
Unity3d Add Nuget Package
Unity Nuget Package Manager

While there's no built-in support for NuGet yet, this might change soon since a lot is happening in this regard. With Unity 2018.1,.NET Standard 2.0 finally got supported. This is a huge deal since it makes a lot of libraries accessible to Unity developers. Check out this Unity blog post for some information. Until then, the process is pretty much as you described. Discover the best assets for game making. Choose from our massive catalog of 2D, 3D models, SDKs, templates, and tools to speed up your game development process. Unity3D 1.5.0 Simple, forward-compatible references to ANY Unity assembly on Mac or Windows. Requires NuGet 2.5 or higher. Partial support to directly use a Lua coroutine as a Unity3D coroutine ScriptLoaderBase and all its child can optionally ignore the LUAPATH global The REPL interpreter and ReplInterpreterScriptLoader now consider the LUAPATH52 environment variable.

Don’t know what MoonSharp is ? Read here..

Latest release: 2.0.0.0 | Zip file | Interpreter NuGet | VsCode Debugger NuGet | Remote Debugger NuGet

2019-08-22

Given the lack of updates in the last … “let’s not count” years (ugh!) we are moving moonsharp to a github organization (moonsharp-devs). More people will join the project and hopefully give a needed helping hand.

Also, if you feel like discussing the future of the project, ask question etc. there’s a Discord channel you can join to chat in real time.

Links in this website are slowly being updated to refer to the org.

2016-10-14

MoonSharp goes 2.0!

A lot of great features. First of all, MoonSharp is switching to a model where sources are provided for Unity. Second, a lot of platforms previously totally unsupported (WebGL, Unity WSA, .NET Core) are now working great. Third, the Visual Studio Code debugger becomes the “default” supported debugger. The remote, flash based debugger will still be maintained, but no new features will be added and testing on it will be little.

What’s new:

Visual Studio Code debugging now supports multiple script objects
Support for .NET Core
Support for Unity WebGL
Support for WSA targets at source level
Improved support of other Unity targets
Unity package is now included inside distribution zip file (easier to use and faster to deploy than the asset store)
Stripped source distribution is now included inside distribution zip file (to ease custom framework builds)
Improved compatibility layer for API changes between .NET framework releases
Fixed : NuGet packages for VsCode debugger were broken
Fixed : VsCode debugger breakpoints might get missed
Fixed : VsCode debugger keeps the program running on exit because of a foreground thread
Fixed an issue where hardwiring a delegate generated invalid ctor calls #158 (thanks issingle)

Zip file | Interpreter NuGet | VsCode Debugger NuGet | Remote Debugger NuGet

2016-10-07

MoonSharp 1.7.0.0 was quite short lived and focused on bug fixes.Here it is MoonSharp 1.8.0.0 with a lot of changes and new features!

Support for debugging from Visual Studio Code (see here for details)
Serialization/Deserialization of tables and objects to JSON
JSON library added
Unity Asset Store package - now in “pending approval” stage
Various (breaking) changes to debugger infrastructure
Added optional args to Script.DoFile, Script.DoString and Script.DoStream methods
Fixed issues and added optional args to Script.DoFileAsync, Script.DoStringAsync and Script.DoStreamAsync methods (.NET 4.x and PCL targets only)
Fixed a minor bug in table serialization of string fields

Warning : this version has some minor but breaking changes for custom debuggers. If you have implemented a custom debugger, be prepared to add a couple of new methods to your object (empty methods are enough).

Zip file | Interpreter NuGet | VsCode Debugger NuGet | Remote Debugger NuGet

2016-10-03

After a time of hiatus on the project, MoonSharp 1.7.0.0 got released:

Behaviour of C# functions called using the colon ‘:’ operator can be chosen using the ColonOperatorClrCallbackBehaviour Script option (see also #149).
Vastly improved performance of table insertion #144 (thanks nshibano)
Vastly improved performance of table appends (somewhat related to #144)
Added disposability to debugger host chain #150 (thanks aravol)
Fixed : require didn’t always skip loading already loaded modules
Fixed : Table.Clear crashing #151 (thanks JokieW)
Fixed : Error loading moonsharp.exe #148 (thanks InfectedBytes)
Fixed : Script processing fails on files smaller than 8 bytes … #145 (thanks nagblock)
Fixed : SyntaxErrorException On valid lua syntax #147 (thanks andreluis034)
Fixed : Hexadecimal numbers were accepted with weird prefixes (like 5x1234)
Fixed : MoonSharp clobber syntex error details during require #121 (thanks fgretief)

Zip file | Interpreter NuGet | Debugger NuGet

2016-05-16

MoonSharp 1.6.0.0 released:

Added a RethrowExceptionNested option to Script.GlobalOptions which instead of doing a plain re-throw of exceptions, embeds them in the InnerException property of a new exception object. Useful to simplify handling (newer exceptions are automatically decorated) and to preserve stack traces on Mono/Unity (annoying Mono bug..)
Removed _ENV tables from serialized bytecode (thanks Matija Hustić)
Added non-standard contains, startsWith and endsWith methods to string module.
Refactored the Table class’s Set/Get methods to be more symmetrical, with added RawGet, Remove and Append methods (thanks Francois Retief)
Added strong names (thanks Fernando P. Najera Cano)
Fixed : Events missing add or remove methods could cause a NullReferenceException
Fixed : __newindex metamethod can completely break the MoonSharp VM (bad bad bug)
Fixed : Lexer matched non-western digits as valid numbers (if you are a .NET developer, recommended read: this - ouch)

Zip file | Interpreter NuGet | Debugger NuGet

As a reminder : if you want to send a pull request, please check that it doesn’t break unit tests before sending!

2016-02-09

MoonSharp 1.5.0.1 has been released!

Also, check out the new tutorials sections.

Hardwiring.
DynValue.NewPrimeTable() to create a prime table, that is a table which can be shared between Scripts
Special syntax for table constructor ${ ... } which can be used to declare a “prime” table.
Serialization of prime tables as exchange data format
Created IRegistrationPolicy interface to customize the type registration process
Fixed: changing the first upvalue of a chunk did not change the _ENV of that chunk (#126)
Fixed: UserData.RegisterAssembly was not registering types correctly if no assembly was passed

Zip file | Interpreter NuGet | Debugger NuGet

2016-01-28

Just as a little peek into what is coming. Soon.

Work is going on towards reaching IL2CPP maximum compatibility. Let’s clarify. As now MoonSharp has quite a good degree of compatibility with IL2CPP but it requires registering the scripts manually (or using DoString instead of DoFile) and a lot of painful fiddling with the link.xml file.

But why fiddling with reflection when one can use no reflection at all ? Soon MoonSharp will include a little utility which will take a snapshot of what types are registered for script interop, and will create a C# source file on the fly which allows for no reflection (thus maximum IL2CPP compatibility), faster startup and faster execution, specially on AOT/IL2CPP platforms (like iOS) and in corner cases. At the price of a little more workflow effort (but very little) and some little extra requirements on interop types.. which can handily be solved through proxy objects.

If you are not using Unity or Xamarin, you probably have less reasons to rely on these (desktop .NET and Mono are a lot more powerful), but you’ll still benefit from faster startup and execution.

Sta

Nuget Unity3d