Is there any known issue with inconsistency on Construct 2, in which something may some times not be triggered?
I just released my first Construct game on Steam (http://store.steampowered.com/app/507340/) and one player has reported a weird bug that seems to be an engine inconsistency.
In a given mission where he is escorting a ship, the ship is supposed to, on path arrived, stop and trigger a dialogue. On the first time he played, the ship didn't stop at the path. It just went on moving, passing the location, and there for not triggering the rest of the mission sequence. He restarted the mission and it worked normally.
I never saw this specific error before, nor have any other player or tester reported it so far.
The same player reported that after a later mission, on the ending cutscene, the ships that were supposed to be destroyed when on collision with the hangar just kept on flying, again not triggering the following sequence. Note that in this case the same scene and code is used after every mission, so it doesn't seem like it could be a code issue, but instead some sort of inconsistency: the engine didn't trigger the collision.
Has anyone seen this sort of inconsistency before?
They don't seem to be frequent, but, as the game is now out on sale and these triggers are used many times, I'm worried the issue may come up more often (with more users, more chance of happening).
I'll probably fix both cases with loophole codes, to make sure those inconsistencies have a backup in case they happen, but I thought best to report it here somehow.
* I didn't post this on the Bug forum because I don't have a specific situation and file to show