swirengine 2.1.0

Install · Quick Start · 2.1 Roadmap · Examples · Releases

📊 Project status

Scope: SwirEngine 2.1 - SwirEditor & Creator Workflow
Progress: [##############################] 100.0%
Counter: 10 / 10 milestones
Status: COMPLETE

Active verified development scope: SwirEngine 2.1 — SwirEditor & Creator Workflow
2.1 roadmap: 10/10 milestones = 100.0% — COMPLETE
2.1 release: PUBLISHED — GitHub Release and PyPI verified
Latest public stable release: SwirEngine 2.1.0
Release date: 2026-09-23
Release source: immutable tag v2.1.0; exact source identity is preserved by release provenance and SHA-256 checksums.

SwirEngine 2.1.0 is publicly released on GitHub and PyPI and is the current stable package. The finite ROADMAP_2_1.md scope is complete at 10/10: it delivers the project-backed SwirEditor, multi-scene authoring, runtime-backed gameplay tooling, production viewport, asset workflows, Play/Debug/Profiler, Build/Export Wizard and verified 2D, 3D and multiplayer shipping paths. Release artifacts are bound to the immutable v2.1.0 source and accompanied by deterministic SHA-256 checksums and provenance.

Stable 2.0 maintenance is no longer tracked as a separate active progress scope. Historical audit evidence remains preserved, and concrete regressions, compatibility failures, security/safety issues or release-blocking defects still reopen focused maintenance when discovered.

✨ Highlights

📦 Install

Install the latest public stable release from PyPI:

python -m pip install -U "swirengine==2.1.0"

Optional audio support:

python -m pip install -U "swirengine[audio]==2.1.0"

Source development:

git clone https://github.com/Swir/SwirEngine.git
cd SwirEngine
python -m pip install -e ".[dev]"

The verified base-engine matrix covers maintained 64-bit CPython 3.10–3.14 jobs across hosted Windows, Linux and macOS runners. This is not a blanket claim for 32-bit Python, PyPy, free-threaded CPython, all CPU architectures or every optional dependency. See docs/SUPPORT_MATRIX_2_0.md.

🚀 Quick Start

2D

from swirengine import Color, Game, Rectangle2D

game = Game("My 2D Game", 1280, 720, mode="2d")
player = game.add(Rectangle2D(0, 0, 120, 70, Color(0.1, 0.75, 1.0, 1.0)))

@game.update
def update(dt):
    speed = 380
    if game.key("A"):
        player.x -= speed * dt
    if game.key("D"):
        player.x += speed * dt

game.run()

3D

from swirengine import Color, Cube3D, Game, Vec3

game = Game("My 3D Game", 1280, 720, mode="3d")
cube = game.add(Cube3D(position=Vec3(0, 0, -4), color=Color(0.2, 0.7, 1.0, 1.0)))

@game.update
def update(dt):
    cube.rotation.y += 50 * dt
    cube.rotation.x += 25 * dt

game.run()

🧭 Active development and stable maintenance

SwirEngine 2.1.0 is the current public stable release. Its completed source roadmap remains preserved as verification evidence while the next development roadmap is defined:

• ROADMAP_2_1.md — 2.1 SwirEditor & Creator Workflow, 10/10 = 100.0%, source roadmap complete; publication pending.

Historical release-development detail remains preserved in ROADMAP_2_0.md, which is 10/10 = 100.0% only for its named source-development scope. The former 2.0 post-release audit is retained as a historical verification snapshot rather than a parallel active roadmap.

Key documentation

• ROADMAP_2_1.md — completed 2.1 editor/creator source roadmap
• docs/MIGRATING_TO_2_1.md — 2.0 → 2.1 migration guidance for source development
• docs/RELEASE_GATE_2_1.md — 2.1 milestone acceptance and publication boundary
• ROADMAP_2_0.md — historical 2.0 source-development roadmap
• docs/SWIRENGINE_2_0_POST_RELEASE_AUDIT.md — archived post-release verification snapshot
• docs/SWIRENGINE_2_0_RUNTIME_LIFECYCLE_AUDIT.md — verified 2.0 lifecycle evidence
• docs/MIGRATING_TO_2_0.md
• docs/public_api_2_0.json
• docs/API_STABILITY.md
• docs/CREATOR_WORKFLOW_2_0.md
• docs/MULTIPLAYER_PRODUCTION_2_0.md
• docs/RUNTIME_SCALABILITY_2_0.md
• docs/SUPPORT_MATRIX_2_0.md
• docs/REAL_GAME_SHIPPING_2_0.md
• docs/PACKAGING_SHIPPING_2_0.md
• docs/PERFORMANCE_EVIDENCE_2_0.md
• docs/RELEASE_SAFETY_2_0.md
• docs/RELEASE_GATE_2_0.md
• docs/SWIRENGINE_2_0_READINESS_AUDIT.md — pre-release readiness evidence

🎮 Real-game integration fixtures

Representative projects are source-only engine integration fixtures and do not receive separate releases:

• SwirEngine 2D Game Demo — examples/2d_game_demo/
• SwirEngine 3D Game Demo — examples/3d_game_demo/
• SwirEngine Multiplayer Game Demo — examples/multiplayer_game_demo/
• Neon Frontier 1.3 — locked historical compatibility fixture
• Neon Frontier 1.4 — locked compatibility/showcase fixture
• Neon Cube Hunt 3D — OpenGL + packaged-runtime regression arena
• Neon Snake 3D — complete 3D regression project

The maintained shipping and compatibility gates drive representative fixtures through creator preparation, source runtime, deterministic staged export, staged runtime, settings/save boundaries, scene/content integrity, UI focus/navigation/activation and privacy-safe diagnostics. Fixture failures are engine integration failures, not demo-only issues.

🧪 Development and verification

python -m pip install -e ".[dev]"
pytest
ruff check src tests examples demo_projects tools
python -m compileall -q src tests examples demo_projects tools
python tools/generate_progress_svg.py --check
python tools/verify_2_1_release_readiness.py
python tools/verify_2_0_release_candidate.py --require-final
python tools/verify_creator_workflow_2_0.py
python tools/verify_runtime_scalability_2_0.py
python tools/verify_platform_matrix_2_0.py
python tools/verify_real_game_shipping_2_0.py
python tools/verify_performance_evidence_2_0.py --output build/performance-evidence.json
python tools/verify_release_safety_2_0.py

tools/generate_progress_svg.py deterministically derives the PyPI-safe README ASCII progress block and the internal/roadmap SVG assets from the same verified 2.1 checklist. Presentation tests verify source math, the exact ASCII percentage/counter, the absence of README progress SVGs, bounded SVG fill geometry, the single roadmap mini, the template contract and legacy-meter cleanup outside the explicit PyPI exception.

🧱 Architecture and technology

SwirEngine keeps a high-level Python creator surface over modular runtime systems. The repository contains rendering, scene/ECS, assets, serialization, physics, audio, input/UI, networking, editor, diagnostics and export/shipping modules with focused regression workflows. Advanced systems remain available through explicit APIs instead of being hidden behind one monolithic game object.

Engineering quality is evaluated against complete games, public installation, resource lifetime, deterministic tooling, creator workflow, failure handling and shipping behavior—not feature count alone.

🔒 API and release policy

• v1.4.0, v1.5.0 and v2.0.0 are immutable published releases; release history is not rewritten.
• 2.1.0 is the latest public stable package.
• 1.6, 1.7, 1.8 and 1.9 remain completed source-only checkpoints and were never published as releases.
• The 2D, 3D and multiplayer game demos remain source-only integration fixtures.
• The published 1.5.0 swirengine.__all__ surface remains the documented starting compatibility floor for 2.0 migration validation.
• Breaking post-2.0 changes require explicit engineering justification, migration documentation and tests.
• SwirEngine 2.1.0 is published from its guarded release gate; the 10/10 roadmap remains the preserved acceptance record for that release.
• A completed historical roadmap does not imply literal perfection; concrete stable-line regressions still reopen focused maintenance.

🗺 Roadmaps and active development

⚠️ Current limitations

• SwirEngine 2.1.0 is published; future feature work must begin under a new explicit roadmap rather than silently widening the completed 2.1 scope.
• The verified base-engine matrix covers only the maintained 64-bit hosted runner architectures exercised by CI; 32-bit Python, PyPy, free-threaded CPython and unverified architectures are not claimed.
• Optional extras such as audio require their own dependency/runtime evidence beyond the base-engine support matrix.
• Desktop build plans are host-native; unsupported cross-compilation is intentionally rejected.
• The dedicated-server contract is headless and deterministic but does not claim public matchmaking, hosting infrastructure or universal transport support.
• Cross-engine FPS, latency and memory superiority rankings remain intentionally unclaimed without an identical maintained comparison harness.

🔎 Search Keywords

Python game engine · Python 2D engine · Python 3D engine · Python multiplayer engine · pip game engine · game development Python · OpenGL Python game engine · scene prefab engine · Python ECS · Python physics engine · Python game editor · SwirEditor · desktop game packaging · PyInstaller game build · game engine networking · SwirEngine