Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

feature: a "works in my engine" filter, so UE-only content stops sitting beside CC0 packs in the same results

Cerrado
  • ¿Algo no está bien?
#160 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
55/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
javascript
Área
frontend

Línea de trabajo

Start with site/public/app.js DEFAULTS and search.mjs CHOICES and passesFilters, then inspect data.json engine fields and site/lib/shared.mjs:17-23 for existing labels. Add the engine selection across filtering, URL state, active-filter chips, stack pages, and UE-only facts. Done when ?engine=godot excludes UE-only entries, ranks Godot-tagged entries first, and UE-only facts show the lock in the first row.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

feature priority: medium

Why it matters

The question a game developer actually asks is "can I use this in Godot / Unity / Unreal?". Epic UE-only content (Paragon, City Sample, ALS) is not usable outside Unreal, yet it appears next to CC0 packs in the same search with only a small "UE only" badge; conversely Godot users cannot find the 31 godot-tagged entries without knowing the tag.

Evidence (at 69387df)

  • data.json entries carry engine_lock (unreal; labels in site/lib/shared.mjs:17-23), ue_versions and hardware_tags. Tag counts: unreal-engine 22, godot 31, godot-4 22, unity 1, engine-agnostic 1.
  • site/public/app.js DEFAULTS (lines 21-33) and search.mjs CHOICES expose no engine state; passesFilters (search.mjs:73-86) never reads engine_lock.

Suggested approach

Add an "Engine" select (Any / Godot / Unity / Unreal / engine-agnostic) that hides entries whose engine_lock does not match and ranks engine-tagged entries first; carry it in the URL (engine=) and in the active-filter chips; show the engine fact on stack pages and in the first row of the facts panel on UE-only entries. Normalising the engine tags (godot vs godot-4, unreal vs unreal-engine) can ride on #96.

Done when

?engine=godot returns no UE-only entries and lists Godot-tagged ones first; the facts panel on UE-only entries states the lock in the first row.

Lenguaje dominante
JavaScript
Estrellas
58
Forks
15
Merge medio
16 h 53 min
PR fusionados (30 d)
14

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de TMHSDigital/Free-Game-Dev-Assets

Todos los issues de TMHSDigital/Free-Game-Dev-Assets

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.