ck-game-angelscript-gameplay

Standardize gameplay logic in the CkFoundation ECS framework using AngelScript.

4|Updated Aug 15, 2023
One-click install
npx skills add https://github.com/chainkemists/CkFoundation --skill ck-game-angelscript-gameplay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck-game-angelscript-gameplay
Source: https://github.com/chainkemists/CkFoundation/tree/main/.claude/skills/ck-game-angelscript-gameplay
Command: npx skills add https://github.com/chainkemists/CkFoundation --skill ck-game-angelscript-gameplay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves the complexity of writing gameplay logic within the CkFoundation ECS framework, preventing common pitfalls like deferred mutation errors, handle invalidation, and improper signal binding.

Core Features & Use Cases

  • Gameplay Idioms: Provides verified patterns for signal binding, deferred requests, and entity composition using AngelScript.
  • Workflow Optimization: Guides the user through the hot-reload cycle, headless compile gates, and the decision-making process for when to drop to C++.
  • Use Case: When implementing a new gameplay feature like a day-night cycle or an inventory system, use this skill to ensure your processors, fragments, and utils follow the framework's strict determinism and replication contracts.

Quick Start

Use the ck-game-angelscript-gameplay skill to verify the correct implementation pattern for a new entity script processor and its associated signal binding.

Frequently Asked Questions about ck-game-angelscript-gameplay

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement gameplay logic in AngelScript for an ECS framework without breaking determinism?

To implement gameplay logic in AngelScript, standardize your entity scripts and processors to strictly adhere to framework determinism and replication contracts. This ensures proper handle validation and prevents deferred mutation errors.

Why does my AngelScript entity processor cause handle invalidation during the hot-reload cycle?

Handle invalidation in AngelScript processors occurs when deferred mutation patterns are improperly applied. Following strict performance scoping and verified signal binding patterns ensures handles remain valid during hot-reload cycles.

When do I need to drop from AngelScript to C++ for Unreal Engine gameplay logic?

You should drop to C++ from AngelScript when gameplay logic exceeds strict performance scoping limits. Use headless compile gates to verify if your processors and feature utils require C++ optimization.

What is the best way to bind signals in AngelScript for an ECS gameplay feature like an inventory system?

The best way to bind signals for an inventory system is using verified gameplay idioms. This ensures your entity composition and processors follow framework-specific replication contracts and avoid deferred request errors.

Can I use AngelScript to write gameplay processors for CkFoundation without causing replication desync?

Yes, you can write processors in AngelScript without desync by enforcing strict determinism contracts. The framework validates feature utils and processors to ensure proper replication across the ECS.