Thanks for your support!
Yes you're right! The enemies AI feeing a bit slow is both my intention and a workaround. The AI sensitivity in fact represented by how frequently an enemy updates its path to the player by running A* pathfinding. If enemies always run the A* pathfinding, then the enemies will always stick to the player without any rest. That'd be a real difficult mode.
But the main reason is that the NavMesh A* pathfinding is a CPU killer and I didn't know of any way to optimize. The larger the map is generated x more enemies on map, the more likely the game is going to get laggy. Thus I did 3 things:
- Make map generation smaller in room / corridor sizes
- Make AI pathfinding less frequent
- But I am able to discriminate different AI's reaction time (green guys react slower, red guys / boss react still fast enough to catch up with the player) Attempt to keep the boss intelligent enough.
Also If playing in browser feels laggy - maybe download offline version and try again - usually performs better!
Oh wait - you mean - you are able to beat the boss with like 2-3 tries? Man that's awesome! You're a legend! You've nailed it. In order to optimize the defeating time as well as conserving precious hitpoints, one should skip unnecessary fights as demonstrated in my walkthrough video.
And there's one roguelike thing I have missed putting in - the presence of corridor traps, spikes, rope plants, poisonous mushrooms, speed mushrooms, locked exits, teleportations, sentry cannons - which should be able to enforce speedrunning players into some battles - prevent players to run freely while allowing 3rd-party methods to execute the enemies. This would preserve some fun for pro players.
A a big con for Roguelike games is there's no way to conclude the officially fastest speedrunning time other than by luck - the same applies to Minesweeper speedrunning. My solution is to hold time-limited competition events with Fixed Seed Numbers so I have Fixed Proc Gen Maps for fair judgement