daid / daid/EmptyEpsilon

Making Hacking a little less random

Open
#467 16 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Lua
Stars
869
Forks
222
Avg merge
18h 33m
Merged PRs (30d)
1

Description

I was playing the relay role the other day, and I was a little bit angry at the fact that, like most minesweeper games, the mines were arbitrarily set up. This leads to situations where the "correct" answer is logically unsolvable and it is impossible for the player to know the result without guessing.

I know it's a small thing, so I'd like to see it with deterministic puzzle where there is no guessing necessary.

Also since we are talking about hacking, what are people's thoughts on having flags/markers to denote bombs, as found in other minesweeper variants.

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start by reviewing the hacking relay role and its current mine setup. Clarify the intended deterministic, no-guess puzzle behavior and whether bomb flags or markers are required. Done means the feature scope is agreed and the hacking puzzle can be completed without guessing, with marker behavior matching that decision.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.