VNGGames SDK Upgrade Guides
Moving to a newer VNGGames SDK version? Each platform has its own upgrade guide covering the breaking changes, deprecations, new APIs, and behavioral changes between releases, with the exact migration steps for the jump you are making.
Platforms with an upgrade guide
iOS
Swift / Objective-C38 documented changes across 28 releases
3.0.0 → 3.19.0
Android
Kotlin / Java32 documented changes across 27 releases
2.5.1 → 3.19.0
Unity
C#23 documented changes across 24 releases
1.1.0 → 1.19.0
Windows
C++22 documented changes across 34 releases
1.1.0 → 2.9.0
Unreal
C++ / Blueprint19 documented changes across 5 releases
1.0.0 → 1.4.1
What each guide covers
Every documented change is one card, tagged with the release it landed in and one of four kinds:
- Breaking: code that built and ran before needs an edit to keep working.
- Deprecation: the old call still works but is on its way out. Move at your convenience, ahead of the removal.
- New: an API that did not exist before, to adopt if you need it.
- Behavioral: the same call, a different result. Nothing to rewrite, but check what your game assumed.
Each card says what changed and why, shows the before and after, and lists the steps to migrate. A card that a later release already superseded drops out, so a long jump never walks you through a step a newer change undid.
How a guide is tailored to your game
A guide opens from the link for your game. That link carries the version the game is on, the version it is moving to, and the features it integrates, so the guide shows only the changes that apply. Either version can be changed at the top of the guide to widen or narrow the range.
Ready to upgrade
Open your platform’s guide with the link for your game. Start with the removal steps at the top, which cover swapping the old SDK for the new one, then work through the cards in release order.