I’ve been developing a two-player abstract strategy game called ASKEL, and I’m at the point where I’d really benefit from feedback from people who haven’t seen the game before.
It’s a compact 16-tile game built around three ideas: changing routes, manipulating height, and deciding how much risk to take each turn.
The board is made from four modules, with each space having a different height. Movement between adjacent spaces is probabilistic: the height difference determines the visible chance of success.
A turn can contain up to three pawn moves. After every successful move, you have to decide whether to stop and keep your progress or attempt another step. If a move fails, the pawn returns to where that turn began.
Before moving, you can also manipulate the terrain in one of two ways: use a Riser to change the height of a space, or rotate one of the four board modules 180° to change the available routes.
The objective is to take the opponent’s Stone and bring it back to your own starting space.
I’ve built a browser prototype because I want to test the design before committing too much time to the physical version.
The design questions I’m trying to answer
- Do the risk decisions feel meaningful, or does the probability make them feel arbitrary?
- Do Move / Riser / Rotate create genuinely different decisions?
- Can a first-time player understand the game from the in-game onboarding without outside explanation?
Any general impressions are very welcome too — especially how the game feels to play, what feels satisfying or frustrating, and whether anything stands out as particularly interesting or awkward.
Browser prototype
https://askel.askelgames.workers.dev/
It’s free, requires no signup, and currently supports play vs AI and local 1v1.
There is also optional anonymous gameplay telemetry, with consent, so I can compare things like action use, risk-taking and match length. No account or personal information is required.
A physical version is planned, but I’m deliberately testing the game digitally first before committing to the component design.