⚠️

重要前提

安装AI Skills的关键前提是：必须科学上网，且开启TUN模式，这一点至关重要，直接决定安装能否顺利完成，在此郑重提醒三遍：科学上网，科学上网，科学上网。查看完整安装教程 →

Godot复活重生机制框架：集成《只狼》《黑魂》式风险回报系统

godot-mechanic-revival by thedivergentai/gd-agentic-skills

47 周安装量

59 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/thedivergentai/gd-agentic-skills --skill godot-mechanic-revival

Go 系统架构游戏

🇨🇳中文介绍

复活与重生机制

概述

此技能提供了一个处理玩家死亡与回归的健壮框架。它超越了简单的"游戏结束"画面，集成了类似《只狼》、《哈迪斯》或《黑暗之魂》中的风险/回报系统。

切勿执行（专家复活规则）

生命周期与状态

切勿让玩家带着现有速度重生 — 务必在 revival_state_reset_guard.gd 中将 velocity 和 angular_velocity 归零，否则玩家重生时会撞向墙壁。
切勿仅凭距离信任最近的检查点 — 务必使用'进度索引' (revival_checkpoint_validator.gd)。非线性游戏中的玩家可能会走回起始区域；不要因此降低他们的重生点。
切勿跳过'无敌帧' — 在危险区域内或敌人附近重生时，如果没有 2 秒的无敌缓冲，会导致"死亡循环"并让玩家感到沮丧。

持久化与数据

切勿仅将检查点保存在 RAM 中 — 如果游戏崩溃，玩家将丢失进度。使用 revival_checkpoint_persistence.gd 立即写入 user://。

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

🇺🇸English

Revival & Resurrection Mechanics

Overview

This skill provides a robust framework for handling player mortality and return. It moves beyond simple "Game Over" screens to integrated risk/reward systems like those found in Sekiro , Hades , or Dark Souls.

NEVER Do (Expert Revival Rules)

Lifecycle & State

NEVER respawn the player with existing velocity — Always zero out velocity and angular_velocity in revival_state_reset_guard.gd or the player will fly into a wall upon respawning.
NEVER trust the nearest checkpoint by distance — Always use a 'Progress Index' (revival_checkpoint_validator.gd). Players in non-linear games may wander back to the start area; don't downgrade their respawn point.
NEVER skip 'Invincibility Frames' (I-frames) — Respawning inside a hazard or near an enemy without a 2s invincibility buffer leads to "Death Loops" and player frustration.

Persistence & Data

NEVER save checkpoints solely in RAM — If the game crashes, the player loses progress. Use revival_checkpoint_persistence.gd to write to user:// immediately.
NEVER hardcode checkpoint coordinates — Use Marker3D or Area3D nodes in the scene. Hardcoded coords break as soon as level geometry changes.
NEVER delete the player node on death — queue_free()ing the player breaks UI refs and references from enemies. Disable processing, hide the mesh, and 'Revive' the existing instance instead.

UX & Pacing

NEVER respawn instantly — An instant snap is disorienting. Always use a 1-2s delay with a screen fade or death animation to allow the player to process the failure.
NEVER reset the entire world on player death — In modern design, opened doors and collected unique items should stay persisted. Use a bitmask in the checkpoint resource to track 'World Progress'.