[X] I have read and understand the suggestion guidelines
Checked for duplicate suggestions
[X] I checked for existing similar suggestions
Summary
People are sometimes confused with the pathfinding behavior, such as why is there no path found or why the behavior chooses the path it does.
Possible workarounds or alternatives
Manually debug by looping through each cell to test if it is an obstacle and display a sprite to show the state on layout start. This isn't ideal as a newer user might not be knowledgeable enough to do so, and may even make mistakes when attempting, causing further confusion and frustration.
Proposed solution
An overlay in the editor that can show the user the pathfinding grid and obstacles, similar to the images shown in the manual (https://www.construct.net/en/make-games/manuals/construct-3/behavior-reference/pathfinding), would give a user immediate feedback regarding the state of the obstacle map when changing pathfinding properties such as cell size and cell border.
Why is this idea important?
This would be a quality of life improvement and make a common but complex feature easier to use for beginners.
DieppedalleDavid
commented
1 month ago
Reviewed guidelines
Checked for duplicate suggestions
Summary
People are sometimes confused with the pathfinding behavior, such as why is there no path found or why the behavior chooses the path it does.
Possible workarounds or alternatives
Manually debug by looping through each cell to test if it is an obstacle and display a sprite to show the state on layout start. This isn't ideal as a newer user might not be knowledgeable enough to do so, and may even make mistakes when attempting, causing further confusion and frustration.
Proposed solution
An overlay in the editor that can show the user the pathfinding grid and obstacles, similar to the images shown in the manual (https://www.construct.net/en/make-games/manuals/construct-3/behavior-reference/pathfinding), would give a user immediate feedback regarding the state of the obstacle map when changing pathfinding properties such as cell size and cell border.
Why is this idea important?
This would be a quality of life improvement and make a common but complex feature easier to use for beginners.
Additional remarks
No response