P
petfriendamy
Guest
Thank you for making such a great piece of software! Thought I should mention some of the glitches I've encountered:
-The white text in dark mode turns black whenever you edit a script.
-It sometimes crashes when you switch between flevel files and then edit something.
-Opening the walkmesh viewer marks the file as having unsaved changes, even if you didn't actually change anything.
-The "Red XIII is named Nanaki" custom opcode doesn't seem to work. I tried using it and the game just hung. (It also didn't create a collapsible code block like if statements usually do.)
-Looks like Cloudiar reported this already, but I noticed, when working with large amounts of if statements, that the game started behaving strangely. When I closed and reopened the file, all the goto statements were changed to "forward %n bytes", with all the corresponding labels missing:
(That screenshot also shows the black text issue I mentioned)
And one suggestion I have, I've noticed that animation type 2 usually waits for the animation to finish before continuing (while type 1 doesn't), but for "play animation and return to previous state," it's reversed. It would be nice if that were fixed—or, better yet, if it actually said something like "waiting for end to continue" on the frontend, so you don't have to memorize which is which.
Keep up the good work!
-The white text in dark mode turns black whenever you edit a script.
-It sometimes crashes when you switch between flevel files and then edit something.
-Opening the walkmesh viewer marks the file as having unsaved changes, even if you didn't actually change anything.
-The "Red XIII is named Nanaki" custom opcode doesn't seem to work. I tried using it and the game just hung. (It also didn't create a collapsible code block like if statements usually do.)
-Looks like Cloudiar reported this already, but I noticed, when working with large amounts of if statements, that the game started behaving strangely. When I closed and reopened the file, all the goto statements were changed to "forward %n bytes", with all the corresponding labels missing:
(That screenshot also shows the black text issue I mentioned)
And one suggestion I have, I've noticed that animation type 2 usually waits for the animation to finish before continuing (while type 1 doesn't), but for "play animation and return to previous state," it's reversed. It would be nice if that were fixed—or, better yet, if it actually said something like "waiting for end to continue" on the frontend, so you don't have to memorize which is which.
Keep up the good work!