Fixing Issues
First,
Fixing bugs requires a basic understanding of JavaScript and HTML. If you feel like you're lacking in these areas, go through all of our intros and tutorials before working on a file as complex as a gaming integration. We learned how to identify issues on the previous page, so let's start by assuming we already know what's wrong.
Now that we’ve found the issue, keep your fix simple and safe. I can't hold your hand through this process, but remember that the best solutions are the ones that run the fastest with the least amount of code. Verify that your solution works by:
- Strategically placing console logs to test sections of code
- Testing your code on recorded video
- Testing your code in-game
This process moves from "fastest checked" to "slowest checked" and is important to follow for efficiency’s sake. If you feel the need to add a meter to fix your effect, include this information at the top of your testing report. Meters are premium and, for the most part, are COMPLETELY laid out by the LightScript department in the first few days of development. Adding a meter should be your absolute last resort to fix an issue and will be looked upon with suspicion while being verified.
Next,
Once you have recorded, identified, fixed, and tested your issue, contact the LightScript department. All code must be reviewed here before we push to the engine. Submissions not following our standards (video evidence, description of the problem, resolutions where the problem is present, documentation of the fix, and documentation of testing) will not be reviewed by the department due to the complexity involved in verifying undocumented work.