RPG Combat Toolkit support

Technical support, clearly routed.

This is the official support policy for RPG Combat Toolkit version 1.0. Use it for installation problems, package-origin errors, reproducible bugs, documented toolkit behaviour, and clarification of supported extension points.

Official email supportEnglishMonday–Friday

Before contacting support

Four checks solve many setup issues.

They also give us the evidence needed to diagnose a remaining issue efficiently.

  1. 01

    Confirm requirements

    Use a claimed Unity 6 editor line, install the Input System, import TMP Essential Resources, and use URP for the supplied demos and presentation assets.

  2. 02

    Run scene validation

    Run Tools > TBCS > Getting Started > Validate Current Scene and resolve every reported error or warning.

  3. 03

    Review packaged guidance

    Check the Quick Start, Troubleshooting guide, FAQ, README, and KNOWN_ISSUES file.

  4. 04

    Reduce the reproduction

    Reproduce the issue in the smallest practical scene or clean project and record the exact trigger sequence.

Support request

What to include in your email.

A complete first report reduces follow-up questions and helps distinguish toolkit issues from project-specific configuration.

Environment

  • RPG Combat Toolkit version
  • Exact Unity editor version
  • Input System, URP, UGUI, and TextMesh Pro versions
  • Operating system and relevant build target
  • Whether the issue occurs in a clean import or an existing project

Reproduction

  • Numbered steps that reproduce the issue
  • Expected behaviour and actual behaviour
  • Complete relevant Console messages and stack traces
  • Screenshots or a short video where useful
  • A minimal reproduction project when requested and practical
Protect your project and licences. Do not email credentials, API keys, personal data, or a complete commercial project unless specifically requested. Remove unrelated paid third-party assets from any reproduction package.

Support scope

Product support, with clear boundaries.

The aim is to support the toolkit reliably without conflating a product licence with bespoke development or consulting.

Included support

  • Installation and dependency problems in claimed configurations
  • Package-origin errors and reproducible toolkit bugs
  • Questions about documented features, demos, and editor workflows
  • Clarification of supported interfaces, providers, adapters, and extension points
  • Reasonable help identifying whether an issue originates in TBCS
  • Compatibility questions for Unity versions and package combinations claimed by version 1.0

Outside standard support

  • Designing or implementing a customer’s complete combat system
  • Debugging unrelated project code or reviewing an entire project
  • Building bespoke features or third-party integrations
  • Porting to unsupported versions, pipelines, platforms, or input backends
  • Multiplayer or networking conversion
  • Emergency, on-call, or guaranteed delivery-time support
Requests outside standard product support may be declined or discussed separately. Purchasing RPG Combat Toolkit does not include custom development or consulting services.

Version 1.0 baseline

Supported release context.

Claimed configuration

  • Minimum editor: Unity 6.0 LTS
  • Release validation matrix: Unity 6000.0, 6000.3, and 6000.5
  • Unity Input System required
  • Default runtime UI uses UGUI and TextMesh Pro
  • Supplied demos and presentation assets are authored for URP

Important boundaries

  • Unity 2022.x is not supported by version 1.0
  • Unity 6.6 and newer are not claimed by version 1.0
  • Built-in RP and HDRP presentation are not supplied
  • Persistence is a combat snapshot layer, not file IO or save-slot management
  • Networking and multiplayer synchronization are not included

Still blocked?

Send the complete report.

Use the subject prefix and checklist above so the request can be triaged without unnecessary follow-up.