- Is pierstoval/character-manager a Laravel package?
- No. CharacterManagerBundle is a Symfony bundle, despite often being described in Laravel/PHP package contexts. It uses Symfony bundle conventions, service container configuration, and Doctrine-oriented persistence rather than Laravel service providers, facades, or Eloquent. For a Laravel application, treat it as a porting or reference candidate, not a drop-in dependency.
- Can I install CharacterManagerBundle in a Laravel application?
- Composer may install the package, but that does not make it Laravel-integrated. The bundle expects Symfony-style registration and configuration, and its persistence approach is Doctrine-oriented. On Laravel, direct consumption is not realistic without a port or fork. Reading and reimplementing the domain ideas is usually the honest path.
- Which Laravel versions are supported by CharacterManagerBundle?
- None are declared or tested. The package is Symfony 5-era with Doctrine, and nothing in the v2.1.0 release adds Laravel support. There is no Laravel service provider, configuration file, or Eloquent integration to evaluate against Laravel 10 or 11. Laravel teams should not plan on native compatibility.
- What PHP version does CharacterManagerBundle require?
- Version 2.1.0 raises the minimum PHP requirement from 7.2 to 7.4. PHP 7.4 reached end of life in November 2022, so the declared floor is itself unsupported. The package does not declare or test PHP 8.x support. For shops running PHP 8.2 or 8.3, compatibility remains unverified.
- What does CharacterManagerBundle actually provide for character sheets and stats?
- It provides a skeleton for modeling, storing, and retrieving RPG character data, including structured character models and extensible character types. It is not a complete, validated, authorized, or production-hardened character sheet system. The v2.1.0 release is housekeeping only: dependency removal, CI migration, deprecation cleanup, and a src layout change. Its value is architectural reference more than reusable runtime code.
- Is CharacterManagerBundle production-ready for RPG tools or campaign managers?
- Treat it as an architectural example, not a production dependency for a Laravel shop. There are no production references or community to consult when behavior surprises you, and the release history is low-cadence. The package also does not establish validation, authorization, or hardened domain behavior. Planning should assume you own every line if you adopt it.
- How does CharacterManagerBundle handle Doctrine persistence?
- The package is Doctrine-oriented and structured around Symfony conventions. That makes direct use viable only on a Symfony application with Doctrine, and specifically a Symfony 5-era stack after v2.1.0. A Laravel application using Doctrine still faces bundle registration and configuration mismatches. Forking or reimplementing the persistence layer is more realistic.
- Is CharacterManagerBundle actively maintained?
- It is best described as episodically maintained rather than dead or actively developed. Version 2.1.0 arrived after roughly four years of silence and included a CI migration from Travis to GitHub Actions, which shows a maintainer willing to do upkeep. However, one release does not establish a cadence, and there is no commitment to future releases. Model upstream fixes as a bonus, not a dependency.
- Does CharacterManagerBundle follow semantic versioning reliably?
- There is a concrete concern: v2.1.0 removed Symfony 4 support, which is a breaking change for Symfony 4 users, but it shipped as a minor release rather than a major. That makes version numbers a weak signal for upgrade safety. Gate any upstream update behind a full test run and assume releases may be breaking regardless of the version bump. This is especially important if you fork the package.
- What are alternatives to CharacterManagerBundle for Laravel RPG applications?
- For Laravel, the practical alternatives are building native Eloquent models and domain services, or forking and owning the bundle if its character model closely matches your needs. Reimplementing from the package as a reference avoids Symfony integration costs and lets you target current PHP and Laravel versions. The package's main value is its structure and vocabulary for characters, stats, and character types. It is not a supported Laravel alternative on its own.