Pem's Code Blog

Labor Day weekend gave me an opportunity to implement pathfinding.  Here’s notes on some of what I read.  BFS (breadth first search) explores equally in all directions.  Dijkstra favors lower cost paths.  A* is modified Dijkstra optimized for a single dst (uses heuristic to search towards dst).  A* is the standard pathfinding for games (I also used it in college game projects ~12-14 years ago), so it

mepem37 :: 2016/09/05 (Monday, September 5, 2016) :: HeroQuest, Unreal Engine :: No Comments »

I gave

mepem37 :: 2016/08/07 (Sunday, August 7, 2016) :: HeroQuest, Unreal Engine :: No Comments »

As described in my visibility post, my rules interpretation uses two kinds of visibility

mepem37 :: 2016/07/16 (Saturday, July 16, 2016) :: HeroQuest, Unreal Engine :: No Comments »

My previous post discussed my rules interpretation for visibility (what a Hero can

mepem37 :: 2016/07/11 (Monday, July 11, 2016) :: HeroQuest, Unreal Engine :: No Comments »

I have a childhood memory (I think it really happened!) that when I first tried HeroQuest with my father, without really reading the rule book, I opened the quest book and setup the entire board for the first quest.  On Zargon

mepem37 :: 2016/07/11 (Monday, July 11, 2016) :: HeroQuest, Unreal Engine :: No Comments »

I packaged my game for Android.  Overall it was mostly painless

mepem37 :: 2016/06/30 (Thursday, June 30, 2016) :: HeroQuest, Unreal Engine :: No Comments »

Interpreting Source Material
When porting content from one media to another (such as book/comic to movie) (or doing a remake), the source material gives a lot of guidance, but there are still plenty of decisions to make.  With HeroQuest, I’m leaning heavily towards making it authentic.  But it is a video game, and I’ve decided to have the program do rules and a campaign and AI (unlike the Tabletop Simulator version)

mepem37 :: 2016/06/22 (Wednesday, June 22, 2016) :: HeroQuest, Unreal Engine :: No Comments »

In my prior work post, I described HeroScribe as the

mepem37 :: 2016/06/18 (Saturday, June 18, 2016) :: HeroQuest, Unreal Engine :: No Comments »

A hero can attack diagonally if they use a certain weapon (eg long sword, staff).  This is simple

mepem37 :: 2016/06/11 (Saturday, June 11, 2016) :: HeroQuest, Unreal Engine :: No Comments »

Move
Movement is initiated from the turn menu.  Two movement dice are rolled, then the result is used as the max number of squares to move.  Movements left is displayed on the HUD.  Movement control uses the arrow keys.  Valid moves are highlighted.

Heroes and monsters are blocked by walls, by certain square space occupants (eg furniture, block tiles), and by board edges.  Each room wall is shared by two squares.  A square occupant can occupy multiple squares including blocking (eg furniture) and non-blocking (eg stair tile) occupants.

Monsters can move through other monsters (but not heroes).  Heroes can move through other heroes (but not monsters).  However, a hero can

mepem37 :: 2016/05/22 (Sunday, May 22, 2016) :: HeroQuest, Unreal Engine :: No Comments »