跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
其他技能

bevy-3d-lighting

Docs-first stub for Bevy 3D lights. Godot counterpart: godot-3d-lighting. Keywords: Bevy, lighting, directional, point, spot, bevy_light, PBR.

thedivergentai · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add thedivergentai/Game-Design-Agentic-Skills --skill bevy-3d-lighting

技能说明


name: bevy-3d-lighting description: "Docs-first stub for Bevy 3D lights. Godot counterpart: godot-3d-lighting. Keywords: Bevy, lighting, directional, point, spot, bevy_light, PBR."

Bevy 3D lighting (docs-first stub)

Not a full port. Docs-first stub. Godot counterpart: godot-3d-lighting.

When to use

Load this when a 3D scene needs lights. Materials stay on bevy-3d-materials. Shadows and GI settings beyond the module blurbs are gaps.

ECS shape

  • Module: bevy::light says it provides directional, point, and spot lights, plus light probes, atmosphere, volumetrics, and shadow configuration.
  • Feature: bevy_light is described the same way on the crate feature list.
  • PBR page names: DirectionalLightViewEntities, ExtractedDirectionalLight, ExtractedPointLight, ExtractedRectLight, GpuClusteredLight (point, spot, or rectangle), DistanceFog, LightProbePlugin, ContactShadows.
  • Systems: light clustering and extraction are engine-owned. Gameplay only spawns light entities.

Godot idea to Bevy idiom

IdeaBevy idiom (idea only)
SunA directional light entity. Struct method list was not opened; the module states the kind exists.
Omni or pointA point light. Same limit.
SpotA spot light. Same limit.
FogDistanceFog on the pbr page.
Baked GIIrradiance volumes are a pbr module. Baking steps were not opened.

Gaps

  • Individual light struct pages (DirectionalLight, PointLight, SpotLight) were not opened, so fields such as intensity or shadow cascades are not named here.
  • bevy_solari is an experimental raytraced-lighting feature. Its API was not opened.
  • Lightmap baking workflows were not opened.

Expert Knowledge Delta

Library target in prose: Bevy 0.20.0. Lattice URLs stay unversioned.

Opened canon only: Component, Resource, Query, Commands, Startup, Update, Fixed / FixedMain (bevy::time), .chain(), Plugin, DefaultPlugins, MinimalPlugins. Messages and observers are an ownership slot. This file does not invent their struct APIs. Systems run in parallel unless .chain() orders the ones that conflict.

Who owns state

PieceOwnerWho may mutateSchedule
Data on one entityComponentOne system via QueryUpdate or FixedMain
One value for the whole appResourceOne systemStartup to insert, then the schedule that reads it
SpawnCommandsThe spawning systemStartup for the initial world; later schedules for runtime spawn
Order that must not race.chain()The chained systems onlySame schedule
Plugin boundaryPluginbuild registers systems and resourcesBefore the app runs

Borrow rule: two systems that both mutably query the same component must be ordered (.chain()) or split so only one writes. Unrelated systems stay parallel. That is the ECS page rule, not a guess at a system-set API.

Decision

If you needDo thisDo not
Per-entity dataComponent + QueryA Godot node script
App-wide config or clockResourceCopy the value onto every entity
Stable simulation stepFixedMain and the Fixed clockTie simulation to raw frame Update
Startup spawnCommands in StartupSpawn from a render system
Cross-system notice that is not shared stateMessage or observer slot in bevy-events-messagingA new event type invented in this file
An API this skill did not openA Gaps rowA fabricated crate (solver, navmesh module, net, XR)

Load references/a-gate-notes.md for the same table plus the gap rule.

NEVER

  • Do not put /0.20.0/ in lattice URLs. WHY: permalinks stay on latest. The 0.20.0 pin belongs in prose once.

  • Do not mutably query the same component from two unordered systems. WHY: the schedule runs systems in parallel unless .chain() orders them.

  • Do not invent a physics, navigation, networking, or XR crate here. WHY: those rows are gaps, blocked, or revisit.

  • No Godot light node types. WHY: a Godot port, an unopened API, or a public lie fails the docs-first bar.

  • No Godot types in Bevy code. WHY: a Godot port, an unopened API, or a public lie fails the docs-first bar.

  • No invented APIs or unnamed third-party crates as the chosen solver. WHY: a Godot port, an unopened API, or a public lie fails the docs-first bar.

  • No Creation Station content. WHY: a Godot port, an unopened API, or a public lie fails the docs-first bar.

  • No umbrella skill over Godot and Bevy. WHY: a Godot port, an unopened API, or a public lie fails the docs-first bar.

  • Do not mark this row ported. It is docs_mapped. WHY: a Godot port, an unopened API, or a public lie fails the docs-first bar.

Reference

docs.rs links use the unversioned latest permalink. The library pin on bevy-master stays 0.20.0.

Official Documentation

  • Migration guides - Unversioned hop index.
  • bevy crate - Unversioned API index. Feature list opened for 0.20.0.
  • Assets - Official asset catalog. No third-party crate was selected.
  • Examples - Example tree on the latest branch.
  • ECS - Component, systems, Query, Startup, Update, and .chain().
  • Plugins - Plugin, DefaultPlugins, MinimalPlugins, and add_plugins.
  • bevy::light - Module blurb: directional, point, spot, probes, shadows.
  • bevy::pbr - Extracted lights, fog, probes, contact shadows.

Related Skills

Prerequisites

阅读完整来源 ↗