[MUST READ] Bug Reporting Guide

[Murtaza]

Help Us Improve hyperPad! 🛠️

Hey everyone!

Found a bug? Reporting it properly helps us fix issues faster and keep hyperPad running smoothly for everyone.

Follow this guide to submit an accurate and detailed bug report. 🧵

⚠️ Bug Report Rules

If a post doesn’t follow these rules, it may be removed to keep things organized.

✅ Be Clear and Concise – Keep your description short and straight to the point. No need for long explanations or guesses about the cause—just describe what’s happening. (If you have extra thoughts, use the “Additional Info” section or reply to your post later.)

✅ One Bug Per Post – If you find multiple bugs, make separate threads for each one. This helps us track and fix them properly.

✅ Double-Check Your Behaviours – Before posting, create a small test project to confirm the issue isn’t caused by how your behaviours are set up.

✅ Include a Sample Project (If Possible) – If you can, attach a simple test project that clearly shows the bug. This helps us diagnose the problem faster.

✅ Tell Us Where to Look – If you’re sharing a project file, specify where the bug happens. Mention the scene, object, or behaviour so we don’t have to dig through everything to find it.

✅ Found a Workaround? – If you’ve discovered a temporary fix, let us know! Add it in the “Additional Info” section or as a follow-up reply.

✅ Stay Engaged – If we ask for more info and don’t hear back from you for 30+ days, we’ll assume the bug is no longer an issue and move the post to the “Expired/Can’t Reproduce” section.

By sticking to this format, we can work together to fix bugs on our no code platform much faster! 🚀

Thanks for helping us improve your game dev on iPad experience! 😊