---
source_url: https://www.pubnub.com/docs/sdks/unity/faq
title: FAQ for Unity SDK
updated_at: 2026-06-03T11:43:57.447Z
sdk_name: PubNub Unity SDK
sdk_version: v9.3.0
---

> Documentation Index
> For a curated overview of PubNub documentation, see: https://www.pubnub.com/docs/llms.txt
> For the full list of all documentation pages, see: https://www.pubnub.com/docs/llms-full.txt


# FAQ for Unity SDK

PubNub Unity SDK, use the latest version: v9.3.0

## Why are there two subscribe methods?

The Unity SDK supports a modern, entity-based flow and retains a legacy `Subscribe<string>()` for backward compatibility.

Use the modern flow documented in [Subscribe](https://www.pubnub.com/docs/sdks/unity/api-reference/publish-and-subscribe#subscribe). It creates a `Subscription` or a `SubscriptionSet`, uses an event listener, and can resume from a timetoken using a `SubscriptionCursor`. The legacy builder `pubnub.Subscribe<string>()` is documented in [Subscribe (old)](https://www.pubnub.com/docs/sdks/unity/api-reference/publish-and-subscribe#subscribe-old) and remains for existing applications.

## Why does encryption use AES-128 when CryptoModule is configured?

If you pass the `cipherKey` argument to `Encrypt`, `Decrypt`, `EncryptFile`, or `DecryptFile`, that argument overrides the configured `CryptoModule` for that single operation and uses legacy Advanced Encryption Standard (AES) with 128-bit keys. Omit the `cipherKey` argument to use the `CryptoModule` configuration (AES‑256‑CBC). For partial encryption, create a separate `CryptoModule` instance and call it directly where needed.

For details, refer to [CryptoModule configuration](https://www.pubnub.com/docs/sdks/unity/api-reference/configuration#cryptomodule).

## Terms in this document

* **Entity** - A subscribable object within a PubNub SDK that allows you to perform context-specific operations.
* **Listener** - A function or objectthat reacts to events or messages, like new chat messages or connection updates, letting your app respond in real-time.
* **Timetoken** - A unique identifier for each message that represents the number of 100-nanosecond intervals since January 1, 1970, for example, 16200000000000000.