foolswood / hexagongame Goto Github PK

At the moment you kind of explore all the possible final states, which is neat, so I don't want to drop it, but can get a bit big (especially with shard mazes).

Edges go back onto the other side.

Instead of the buttons

If either shard has never been moved the "win" message does not come up.

I have checked to see if the types of numbers (ints, floats) set in the positions are different when the maze is set up vs. when positions update, but it looks good to me. I can't spot the problem; although I think it didn't exist previously and has arisen since the "allEqual" function was introduced.

If it was curvier so you could see more of where you'd come from and were going to that'd be good.

Maybe a little marker that moves along it to show you the route would be nice too (must be skippable).

Played with 2 shards on a randomly generated 4 colour 5x5 maze, startpoints [1,1] [3,3].

The player that completes it wins or...
the player that first correctly determines that it is impossible to complete the maze.

Guessing incorrectly results in being eliminated from the round.

So it can play with n players (there's probably a practical fun limit, but it's more than the 2 we have for convenient testing).

May want tweaking slightly, but it seems funish.

Yeah, it kinda leaves people guessing right now.

It's got a bit everywhere, and each file can only have one maze.
They should load from JSON (possibly via AJAX, although that makes it more awkward to test) when running normally.

Make it so you can download your state via a data url.

Might also be neat to use some of the HTML5 local storage stuff too.

It seems I still don't understand Github.

I was attempting to use a "pull request" to get your updated code onto my version of the project. I appear to have instead put my mazes onto your version.

When the marker is clicked to return to the start position it doesn't always go there, sometimes it goes to the menu instead.

I suspect this is to do with changing to addEventListener instead of onclick, it'll need some kind of removal code.

Presumably it doesn't redraw under the box anymore.

At all or in all colours?
What if you finished everything, where do you start? - You don't.

It just saves "undefined", which isn't that helpful. Should probably be disabled if we don't have anything to save.

Given there's no endpoint how does this work?

Hexes that have a cycle of colours instead of one.

As always with these ideas working out how to draw it in a non-confusing way is the hardest bit.

People just don't read the instructions page.

In which the aim is to bring the ends together.

!No idea if this is interesting!

When you leave a hex you swap colours with it instead of adopting its colour.

Solve the maze:

{"maze":["YpWpY","gbrpr","BbG P","rbrpr","RgRgR"],"starts":[[0,1]],"end":[2,0],"startColour":"w"}

The solver will hop around getting back to the beginning so it probably doesn't have that in the list of accessed states.

It should feel like you've achieved something, rather than "what happened" for first time players.