3,253 件 ・ 関連度順
概要と使いどころ
Bevy 0.20 action-RPG router: real-time hits, stats, inventory, and quests as ECS joins, with domain work in the linked skills. Use when routing an action RPG. Keywords: Bevy, action RPG, hits, stamina, quests, ECS, router.
日本語の概要は準備中です。原文の説明を表示しています。
Route a Bevy 0.20 educational loop. Use when prompts and choices are components, lesson totals are one resource, and grading must run after selection in one chain. Keywords: Bevy, Educational, LessonProgress, Choice, chain, genre.
日本語の概要は準備中です。原文の説明を表示しています。
Spawn and tune Bevy 0.20 directional, point, and spot lights, cascade shadows, distance fog, and a nearest-light shadow budget. Use when a 3D scene needs a sun, local lights, or fog on the camera. Keywords: DirectionalLight, PointLight, SpotLight, CascadeShadowConfig, DistanceFog, bevy_light.
日本語の概要は準備中です。原文の説明を表示しています。
Bevy 0.20 horror router: sanity, stalker suspicion, and light energy as ECS data, with lighting, audio, and navigation in the linked skills. Use when routing a horror game. Keywords: Bevy, Horror, sanity, stalker, ECS, router.
日本語の概要は準備中です。原文の説明を表示しています。
Bevy 0.20 chase, patrol, and wait policy: an enum brain, a goal, a desired velocity, and a retarget timer on FixedUpdate. Use when an actor must choose a goal before movement. Paths stay on bevy-navigation. Keywords: Brain, Goal, DesiredVelocity, PatrolRoute, FixedUpdate, chase, patrol.
日本語の概要は準備中です。原文の説明を表示しています。
Load Bevy 0.20 assets with AssetServer and spawn scenes with bsn!, spawn_scene, and queue_spawn_scene. Use when content comes from disk, a handle must be ready, or a level root should be replaced. Keywords: AssetServer, Handle, is_loaded_with_dependencies, bsn, Scene, file_watcher, LevelRoot.
日本語の概要は準備中です。原文の説明を表示しています。
Route a Bevy 0.20 idle clicker: one Wallet resource, generator entities, click on Update, offline bank capped in hours. Keywords: Bevy, idle, clicker, Wallet, Generator, offline, chain, ECS.
日本語の概要は準備中です。原文の説明を表示しています。
Bevy 0.20 kinematic character movement: intent components, FixedUpdate integration, coyote time, and jump buffer. Use when a player or actor walks or jumps and the step must stay stable. Keywords: Bevy, movement, FixedUpdate, coyote, jump buffer, ECS.
日本語の概要は準備中です。原文の説明を表示しています。
Route a Bevy 0.20 open world. Use when region membership is a component, the player cell is one resource, and activation runs after the cell write in one chain. Keywords: Bevy, Open world, Resident, PlayerCell, Active, chain, genre.
日本語の概要は準備中です。原文の説明を表示しています。
Bevy 0.20 party router: local seats, shared scores, and minigame swaps as ECS data. Use when routing a local party game. Keywords: Bevy, Party, minigame, score, ECS, router.
日本語の概要は準備中です。原文の説明を表示しています。
Route a Bevy 0.20 platformer: coyote time and jump buffer on Mover, gravity on FixedUpdate, one-way ledges, follow camera. Keywords: Bevy, platformer, coyote, Mover, FixedUpdate, Camera2d, ECS.
日本語の概要は準備中です。原文の説明を表示しています。
Place Bevy 0.20 gameplay data on a Component or a Resource. Use when choosing Query versus Res/ResMut, insert_resource, Time and Timer, or a RON/asset handle stored once for the app. Keywords: Bevy, Resource, Res, ResMut, Component, Timer, AssetServer.
日本語の概要は準備中です。原文の説明を表示しています。
Bevy 0.20 dialogue data: line tables in a resource, the current line index on a component, and choice flags filtered before the write. Use when lines or choices advance. Keywords: Bevy, dialogue, line index, choices, ECS.
日本語の概要は準備中です。原文の説明を表示しています。
Bevy 0.20 rhythm router: chart notes, a song clock, and hit windows as ECS data. Use when routing a rhythm game. Keywords: Bevy, Rhythm, chart, hit window, ECS, router.
日本語の概要は準備中です。原文の説明を表示しています。
Route a Bevy 0.20 roguelike: RunSeed resource, room entities, permadeath flag, turn energy, grid pickup. Keywords: Bevy, roguelike, RunSeed, permadeath, turn, loot, ECS.
日本語の概要は準備中です。原文の説明を表示しています。
Compose Bevy 0.20 entities from small components and systems. Use when spawning tuples with Commands, filtering Query with With, ordering writers with chain, or attaching ChildOf. Keywords: Bevy, ECS, Component, Query, Commands, chain, ChildOf.
日本語の概要は準備中です。原文の説明を表示しています。
Bevy 0.20 collection loop: pickup markers, a quota resource, one score per entity per pass, and NextState when the quota is met. Use when the run is about collecting objects. Keywords: Bevy, collection, pickup, quota, NextState, ECS.
日本語の概要は準備中です。原文の説明を表示しています。
Bevy 0.20 sandbox router: placed cells, remove, and a serde snapshot of the build. Use when routing a sandbox. Keywords: Bevy, Sandbox, place, save, ECS, router.
日本語の概要は準備中です。原文の説明を表示しています。
Route a Bevy 0.20 shooter: projectile entities, hitscan by translation, collide-and-despawn, wave budget resource. Keywords: Bevy, shooter, Projectile, hitscan, Wave, despawn, ECS.
日本語の概要は準備中です。原文の説明を表示しています。
Route a Bevy 0.20 RTS. Use when selection and move orders are components, a control group is one resource, and marching runs after the order write in one chain. Keywords: Bevy, RTS, Selected, MoveOrder, ControlGroup, chain, genre.
日本語の概要は準備中です。原文の説明を表示しています。
Route a Bevy 0.20 simulation. Use when hunger and jobs are components, the sim hour is one resource, and needs run after the clock step in one chain. Keywords: Bevy, Simulation, SimClock, Hunger, Job, FixedUpdate, chain, genre.
日本語の概要は準備中です。原文の説明を表示しています。
Run a Bevy 0.20 time trial as ECS data. Use when a race clock, split gates, and a finish line share one resource and must be chained, while movement steps on FixedUpdate. Keywords: Bevy, time trial, RaceClock, SplitGate, FixedUpdate, chain.
日本語の概要は準備中です。原文の説明を表示しています。
Bevy ECS hub for Bevy 0.20+. Use when starting a Bevy game, choosing ECS boundaries, or picking a Bevy skill. Keywords: Bevy, ECS, bevy-master, schedules, plugins.
日本語の概要は準備中です。原文の説明を表示しています。
Pick the right ComfyUI startup flags for VRAM, attention, caching, and speed. The full decision matrix for OOM (--novram / --cache-none / --disable-smart-memory), shared-VRAM creep on Windows (--reserve-vram N), model-switching with big text encoders (--cache-none), high-VRAM throughput (--gpu-only / --highvram), and attention-backend selection (--use-sage-attention for speed, --use-pytorch-cross-attention as the highest-quality / Z-Image-safe fallback). Also the acceleration-stack + Blackwell/RTX 5000 (sm_120) notes. Use when a graph OOMs (especially long video like LTX 2 / WAN), when the GPU spills into shared VRAM and slows to a crawl, when switching between models eats all RAM, when Z-Image produces black/garbled output under Sage, or when deciding which attention backend to launch with. Flag names verified against upstream comfy/cli_args.py; see Sources.
日本語の概要は準備中です。原文の説明を表示しています。