Far-Beyond-Pulsar/Pulsar-Native

Components in level editor not allowed to have unique field values when multiple components of a type are present

Open

#519 opened on Aug 8, 2026

View on GitHubContributor guide
 (1 comment) (0 reactions) (1 assignee)Rust (29 forks)auto 404
bughelp wantedpriority: highux/design

Repository metrics

Stars
 (348 stars)
PR merge metrics
 (PR metrics pending)

Description

Components in the level editor are not allowed to have unique field values when multiple components of a type are present by the current engine:

This will no doubt be fixed during the SceneDB overhauls

Contributor guide

Research direction
Investigate how the level editor enforces unique field values for components and why it prevents multiple components of the same type from having distinct values. Review SceneDB implementation and relevant tests to identify where this constraint is incorrectly applied. Consider how the upcoming SceneDB overhauls might resolve this and propose a targeted fix.
Tech stack
rust
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
RustGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35