Managed to fix the problem, a node would reset all the edges parents even if they already have one, resulting in a node having a parent that had their Child as the parent -> infinite loop.
simply changed
edge.setParent(currentNode);
To:
if(edge.getParent() == null) edge.setParent(currentNode);
Why is it sketchy to use the manhattan distance between 2 tiles to evaluate the cost of g and h?
I believe the search works since it calls the construct path which then leads to an infinite loop. I think I do something wrong when I set a nodes parent, which is an error Id do same with both...
Hello, my A* implementation have been giving me a headache for the past hours and am now turning here for help.
Here are 2 snippets of my code, 1 snippet is the part of my code that searches through the nodes and do the open/closed list operations and the second snippet is the part that...
One approach is to floodfill all rooms, when you know contents of rooms you can evaluate the room type. Then you can handle the rooms and if you find the boss room go smash him. After writing tailored combat code for each boss of course.
All clients are detectable one way or another. However detected? runemate is not by jagexs current bot defense methods. It annoys me that everyone mixes detected and detectable up all the time.