Help
Ask us anything about Yarn Spinner. Before you write in, have a look at the known issues below. You might find your answer there.
Get in touch
Two ways to reach us. Either is fine.
hello@yarnspinner.dev
Email the team. Best for bug reports, licensing and purchase questions, and anything you'd rather not post publicly. We usually reply within a few business days.
Send an email →Discord
Ask in the community server. Best for "how do I do this?" questions, where other Yarn Spinner users are often the fastest answer.
Join the Discord →What to tell us
The more of this you include, the faster we can help. Copy the list and fill it in if that's easiest.
Which product
Yarn Spinner for Unity, Godot (C# or GDScript), Unreal Engine, the VS Code extension, Story Solver, or Try Yarn Spinner.
Which version
The Yarn Spinner version, and whether it's the free edition or Yarn Spinner+.
Where you got it
Unity Asset Store, itch.io, OpenUPM, GitHub releases or source, the Godot Asset Library, Fab, the VS Code Marketplace, or Open VSX. If you got it somewhere else, tell us where.
Engine and platform
Engine version (e.g. Unity 6000.0.30f1, Godot 4.6), your operating system, and the platform you're building for.
What you did
The steps that lead to the problem, what you expected to happen, and what happened instead.
Errors and code
The full error text or console output, plus the smallest .yarn script or project that shows the problem.
Bought Yarn Spinner+ or an add-on? Mention the store and the account or order you bought it with, so we can check your licence.
Known issues
Problems we know about, and what to do about them. Filter by the product you're using.
IL2CPP build failures in Unity 6.5+ #
Details
Building for any IL2CPP target fails. The build log reports an IL2CPP error for System.Span in the aliased Yarn.System.Memory assembly, ending in "System.InvalidOperationException: Sequence contains no matching element". The cause is the assembly aliasing we apply to prevent DLL collisions. The aliased System.Memory assembly it brings in breaks IL2CPP. We tracked this down with the community, and a fix has been in testing with them since 21 July 2026. It should roll out soon.
No known issues logged for that product.
This list covers issues we've confirmed. It isn't every open bug. Everything we're tracking is in the issues and discussion repo on GitHub.