Puzzle Editor Improvements

Open
#674 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
lua
Domain
game-dev

Research direction

Start by exploring the Puzzle Editor and how it uses GameBase and ClientStack; the issue names no files or tests. First clarify which improvement to tackle and whether the editor should continue to use GameBase. Done should mean a specifically scoped improvement with a way to verify it in the editor.

Written by the indexing model from the issue text.

Description

Client-side priority: 1 - middle
  • needs a way to quickly test a puzzle
  • tabbing out activates the pause menu as if you're in a match
  • there should be keyboard controls to modify the puzzle, not just mouse; that includes navigating to the editor itself which I believe is only accessible by mouse right now
  • for panels without transparency it is hard to see at a glance which one is selected
  • needs a way to modify move count, stop time, shake time
  • some of the options aren't very obvious from just the picture, like setting the cursor start position vs moving the cursor in the playfield
  • Overall I'm not sure if using GameBase as the foundation for the editor is the right approach as a bunch of related problems are from the ClientStack not being particularly made for this. Maybe we can use some of it with compartmentalization but probably not the whole thing.
  • Need a way to add new puzzles at a spot
  • Need a way to add a puzzle for current state in replay
  • Need a way to change puzzle type
  • Polish
Dominant language
Lua
Stars
30
Forks
20
Avg merge
3d 15h
Merged PRs (30d)
17

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from panel-attack/panel-game

All issues in panel-attack/panel-game

Similar issues

More Lua issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.