{"author_name": "hathol", "cat": "LD #29", "comments": [], "epoch": 1398516420, "likes": 0, "metadata": {"p_key": "31923", "p_author": "hathol", "p_authorkey": "35002", "p_urlkey": "67422", "p_title": "Pathfinding done (for now)", "p_cat": "LD #29", "p_event": "LD29", "p_time": "1398516420", "p_likes": "0", "p_comments": "0", "p_status": "UPD5", "us_key": "35002", "us_name": "hathol", "us_username": "hathol", "event_start": "1398384000", "event_key": "22", "event_name": "LD29"}, "text": "

So my initial pathfinding implementation is done. It’s basically a simple node graph with a very unoptimized A* implementation.
\n I was pretty annoyed by how long it took me to write the A*, but hey, it’s been a while since I wrote a pathfinder by myself.

\n

The node graph is just manually placed nodes, nothing fancy there. The reason why I didn’t go with an algorithmic solution for node placement was mainly performance and time constraints. This way I can reduce the number of nodes to the bare minimum and placing so few nodes manually was still faster than doing it in code. It also means I have full control over node placement, so I can hopefully do some more fancy stuff like bridges and tunnels in a later iteration of the level map.

\n

Now it’s on to the AI. Once I’ve got the basic behaviour down I’ll refactor things a bit and implement the AI as a proper state machine so it’s easier to expand the abilities.

\n

I’m slightly behind my schedule, but so far I’m not worried. I’m pretty sure I can get pretty much all of the initial gameplay done by early tomorrow morning, then get a few hours of sleep and spend all of tomorrow on Sound and Art. Hopefully the very core mechanics will be done by around 6pm so I can get a bunch of testers to try things out.

\n

\"pathfinding\"

\n

Alex Out

", "time": "April 26th, 2014 7:47 am", "title": "Pathfinding done (for now)"}