Debug Logging
About​
Debug logging is a setting that can be enabled in the Skillz settings. It enables greater insight into how a Unity or Godot game is interacting with the Skillz SDK.
- Unity/C#
- Godot/GDScript
Using Debug Logging​
- Go to
Skillz > Settingsfrom the menu bar. - Under the
Game Settingssections, select theDebug Loggingoption. - Run the game using SIDEkick in the Unity Editor. Messages will appear in the Console.
- Most debug messages will also appear in Logcat logs when building to mobile devices. Make sure and select the
Development Buildoption in theBuild Settingsto see Unity log messages in Logcat.
Logging Message Types​
[Skillz]​
Interactions with the Skillz API, SDK initialization, or Skillz specific build scripts. Build script messages will always display even if debug logging is off.
[Skillz Editor Settings]​
Loading settings from the Skillz settings.
[Skillz SIDEkick]​
Internal SIDEkick functionality. These will only display when running your game within the Unity editor.
Warnings and Errors​
Warnings and errors are always displayed even if debug logging is off.
Using Debug Logging​
Godot has two separate settings, both false by default:
skillz/debug_loggingin Project Settings turns on the SDK's informational logging on every platform: the native bridges'[native/iOS],[native/android]and[native/stub]lines, the Android plugin'sSkillzGodotlogcat lines (match ids, scores, replay frame counts) and[SkillzReplayCapture]prints. Leave it off in a shipped build; the export guard refuses a Production build with it on.skillz/sidekick/debug_logginggates SIDEkick's own[Skillz SIDEkick]lines in the editor simulator. Toggle it from the Skillz SIDEkick dock or set it directly.
Where the messages appear:
- In the editor, in the Output panel.
- On Android, in Logcat. Filter on the
SkillzGodottag for the plugin andgodotfor your ownprint()calls:adb logcat -s SkillzGodot:* godot:*. - On iOS, in the Xcode console or the device log. Your
print()output arrives asdodge-the-creeps[pid] <Info>lines (your app name in place of the sample's), the SDK's as[Skillz]lines.
Logging Message Types​
[Skillz]​
Facade messages (Skillz.gd): refused scores, requests retired at match end, state warnings. Warnings and errors in this group are never gated.
[native/iOS], [native/android], [native/stub] and SkillzGodot​
The platform bridges. Informational lines (which call was made, with which match id) only with skillz/debug_logging on. The one-line Skillz environment: <name> (<url>) printed at startup is deliberately not gated, so QA can read the environment off any build's log.
[SkillzSDK]​
The export plugin, during an export: injected meta-data, Podfile written, AppLovin step result, privacy-string check. Always displayed.
[Skillz SIDEkick]​
Internal simulator functionality; editor only, gated by skillz/sidekick/debug_logging.
Warnings and Errors​
Warnings and errors are always displayed even if debug logging is off.