graninas/Hydra

Labyrinth: map functionality

Open

#55 opened on Jun 12, 2020

View on GitHub
 (0 comments) (0 reactions) (1 assignee)Haskell (14 forks)github user discovery
advanced taskenhancementgood first issueshowcases

Repository metrics

Stars
 (206 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Idea: to allow the player to track the exploration of the labyrinth. (Hint: the "print" command is a cheating and should be used for debug only.)

Stage 1:

  • To enable this functionality, the player should find a special object in the labyrinth - a "map".
  • The "map" object should be displaced in the labyrinth randomly (like "treasure").
  • The "map" object should be correctly rendered by the rendering functions (it should be visible on "print")
  • The "map" object should be of type "Content".
  • The player should get a flag in the inventory that indicates that the "map" object is found.

Stage 2: Tracking algorithm

  • The "map" command should display where the player has traveled so far.
  • The tracking algorithm can be any (no special requirements).

Hints on data types:

  • Trail can be of types Map.Map ( Map.Map Pos (Cell, Content) ), Set.Set ( Set.Set Pos ) or just a list ( [Pos] )

Hints on how to approach the task:

  • Add a dummy command "map" with some trail predefined and rendered

Contributor guide

Research direction
Implement the map command by first adding a 'map' object that can be found randomly in the labyrinth. Then track the player's path using a data structure like a Set of positions. Finally, render the path when the player has the map.
Tech stack
haskell
Domain
game dev
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
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.
Clear
Prerequisites
HaskellGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75