Troubleshooting Plugins RPG Maker MZ - Revision history

Yanfly at 14:02, 26 January 2025

2025-01-26T14:02:49Z

Yanfly at 14:02, 26 January 2025

2025-01-26T14:02:25Z

Irina at 18:52, 16 December 2024

2024-12-16T18:52:17Z

Irina at 18:43, 16 December 2024

2024-12-16T18:43:26Z

Irina at 18:42, 16 December 2024

2024-12-16T18:42:22Z

Irina at 18:39, 16 December 2024

2024-12-16T18:39:59Z

Irina at 18:32, 16 December 2024

2024-12-16T18:32:49Z

Irina at 18:30, 16 December 2024

2024-12-16T18:30:29Z

Irina at 18:25, 16 December 2024

2024-12-16T18:25:41Z

Irina at 18:16, 10 September 2024

2024-09-10T18:16:24Z

@@ Line 146: / Line 146: @@
 [[File:FindGameFolder.png]]
-Make sure you can open the zipped file before sending it. If we cannot open it, we cannot help you.
+Make sure you can open the zipped file before sending it.
 |-

@@ Line 131: / Line 131: @@
 {| class="wikitable" width="100%"
 | style="background: #595959; font-weight: bold; font-size: 120%" | <h2>Bug Report Step 7.</h2>
 Upload the project online to share with the plugin developer team. [[Visustella|VisuStella]] uses Google Drive to check projects.
@@ Line 140: / Line 163: @@
 {| class="wikitable" width="100%"
-| style="background: #595959; font-weight: bold; font-size: 120%" | <h2>Bug Report Step 8.</h2>
+| style="background: #595959; font-weight: bold; font-size: 120%" | <h2>Bug Report Step 9.</h2>
 [https://forms.gle/E4aPfWdAf1WSWQnN7 Report it to the plugin developer team.]

@@ Line 55: / Line 55: @@
 If it doesn't work there, report it to the plugin developer team by doing as such:
 {| class="wikitable" width="100%"
-| <h2>Bug Report Step 1.</h2>
+|-
 '''Create an empty RPG Maker MZ project or use the VisuStella MZ Sample Project'''
 |-
 | This means ''File > New Project'' or the ''VisuStella MZ Sample Project''. Why is this necessary? Because we need a controlled environment to make sure the bug occurs at the default level and not through a series of unintended event commands and/or script calls.
 If you ''DO NOT'' have a bug report project attached and all you're sending is just a screenshot or video, we will not be able to review the bug. Sending the bug report project is non-negotiable.
 '''WHY''' do we need a bug report project?
@@ Line 75: / Line 78: @@
 {| class="wikitable" width="100%"
-| <h2>Bug Report Step 2.</h2>
+| style="background: #595959; font-weight: bold; font-size: 120%" | <h2>Bug Report Step 2.</h2>
 Include the plugin and any of the required plugins inside of it.<br>'''REMOVE ALL NON-VISUSTELLA MZ PLUGINS!'''
@@ Line 85: / Line 88: @@
 {| class="wikitable" width="100%"
-| <h2>Bug Report Step 3.</h2>
+| style="background: #595959; font-weight: bold; font-size: 120%" | <h2>Bug Report Step 3.</h2>
 '''[[How to Update Plugins RPG Maker MZ|MAKE SURE ALL INCLUDED PLUGINS ARE UPDATED TO THE LATEST VERSION!]]'''
@@ Line 95: / Line 98: @@
 {| class="wikitable" width="100%"
-| <h2>Bug Report Step 4.</h2>
+| style="background: #595959; font-weight: bold; font-size: 120%" | <h2>Bug Report Step 4.</h2>
 Exclude any other plugins that are unrelated to the problem.
@@ Line 105: / Line 108: @@
 {| class="wikitable" width="100%"
-| <h2>Bug Report Step 5.</h2>
+| style="background: #595959; font-weight: bold; font-size: 120%" | <h2>Bug Report Step 5.</h2>
 Recreate the problem for the plugin developer team.<br>MAKE SURE the project works.<br>If it doesn't work due to missing graphical or audio resources, put them in!
@@ Line 117: / Line 120: @@
 {| class="wikitable" width="100%"
-| <h2>Bug Report Step 6.</h2>
+| style="background: #595959; font-weight: bold; font-size: 120%" | <h2>Bug Report Step 6.</h2>
 Write down the steps needed for the plugin developer team to reproduce the problem.
@@ Line 127: / Line 130: @@
 {| class="wikitable" width="100%"
-| <h2>Bug Report Step 7.</h2>
+| style="background: #595959; font-weight: bold; font-size: 120%" | <h2>Bug Report Step 7.</h2>
 Upload the project online to share with the plugin developer team. [[Visustella|VisuStella]] uses Google Drive to check projects.
@@ Line 137: / Line 140: @@
 {| class="wikitable" width="100%"
-| <h2>Bug Report Step 8.</h2>
+| style="background: #595959; font-weight: bold; font-size: 120%" | <h2>Bug Report Step 8.</h2>
 [https://forms.gle/E4aPfWdAf1WSWQnN7 Report it to the plugin developer team.]

@@ Line 70: / Line 70: @@
 Because it's to ensure that the bug we're fixing is ''your'' bug using ''your'' provided conditions. This is our way of personally working with ''you'' on the conditions ''you've'' set for the game, bug in a replicated and separated project. Sending us only a screenshot or video will result in the bug fix getting delayed and a return e-mail saying that we need a bug report project.
 |}
@@ Line 78: / Line 80: @@
 |-
 | VisuStella MZ is '''NOT''' responsible for plugin incompatibilities outside of the VisuStella MZ library as per our Terms of Use conditions.
 |}
@@ Line 86: / Line 90: @@
 |-
 | If your plugin(s) is not the latest version and the latest version fixed the bug for you, you no longer need to get help for it.
 |}
@@ Line 94: / Line 100: @@
 |-
 | This is to ensure that the bug is related to the plugin at hand and not caused by something else.
 |}
@@ Line 104: / Line 112: @@
 Also, '''MAKE SURE''' the project is able to run. We've encountered a LOT of projects that are missing resources needed for it to run, which suggests to us that you didn't test the bug in the project and don't really care enough for it to be fixed.
 |}
@@ Line 112: / Line 122: @@
 |-
 | Just like above, this is to ensure that we are working on the bug that is affect ''your'' game project. If there are no instructions on how to replicate the problem, it will not help you get the bug fixed faster. If your bug requires a bunch of steps to get it replicated and if you do not include those steps, do not expect us to figure it out on our own.
 |}
@@ Line 120: / Line 132: @@
 |-
 | Google Drive is the best way to share your project with us. Do not use other online uploaders.
 |}
@@ Line 128: / Line 142: @@
 |-
 | Please fill out everything to the best of your ability.
 |}

@@ Line 101: / Line 101: @@
 Recreate the problem for the plugin developer team.<br>MAKE SURE the project works.<br>If it doesn't work due to missing graphical or audio resources, put them in!
 |-
-| This is to ensure that we are working on YOUR problem and not something else that we might think is your problem. MAKE SURE the bug can be replicated inside the bug report project.
+| This is to ensure that we are working on ''your'' problem and not something else that we might ''think'' is your problem. The bug must be replicated inside the bug report project.
-Also, make sure the project is able to run. We've encountered a LOT of projects that are missing resources needed for it to run, which suggests to us that you didn't test the bug in the project and don't really care enough for it to be fixed.
+Also, '''MAKE SURE''' the project is able to run. We've encountered a LOT of projects that are missing resources needed for it to run, which suggests to us that you didn't test the bug in the project and don't really care enough for it to be fixed.
 |}
@@ Line 111: / Line 111: @@
 Write down the steps needed for the plugin developer team to reproduce the problem.
 |-
-| Just like above, this is to ensure that we are working on the bug that is affect YOUR game project. If there are no instructions on how to replicate the problem, it will not help you get the bug fixed faster. If your bug requires a bunch of steps to get it replicated, and you do not include those steps, do not expect us to figure it out on our own.
+| Just like above, this is to ensure that we are working on the bug that is affect ''your'' game project. If there are no instructions on how to replicate the problem, it will not help you get the bug fixed faster. If your bug requires a bunch of steps to get it replicated and if you do not include those steps, do not expect us to figure it out on our own.
 |}

@@ Line 57: / Line 57: @@
 {| class="wikitable" width="100%"
-| [[File:Nonnegotiable.png]]
+| <h2>Step 1.</h2>
-Step 1.
+'''Create an empty RPG Maker MZ project or use the VisuStella MZ Sample Project'''
-'''Create an empty RPG Maker MZ project or use the VisuStella MZ Sample Project'''
+[[File:Nonnegotiable.png]]
 |-
 | This means ''File > New Project'' or the ''VisuStella MZ Sample Project''. Why is this necessary? Because we need a controlled environment to make sure the bug occurs at the default level and not through a series of unintended event commands and/or script calls.
@@ Line 68: / Line 68: @@
 Sending us only a screenshot or video will result in the bug fix getting delayed and a return e-mail saying that we need a bug report project.
 |}
 {| class="wikitable" width="100%"
-| Step 2.<br>Include the plugin and any of the required plugins inside of it.<br>'''REMOVE ALL NON-VISUSTELLA MZ PLUGINS!'''
+| <h2>Step 2.</h2>
 |-
 | VisuStella MZ is '''NOT''' responsible for plugin incompatibilities outside of the VisuStella MZ library.
 |}
 {| class="wikitable" width="100%"
-| Step 3.<br>'''[[How to Update Plugins RPG Maker MZ|MAKE SURE ALL INCLUDED PLUGINS ARE UPDATED TO THE LATEST VERSION!]]'''
+| <h2>Step 3.</h2>
 |-
 | If your plugin(s) is not the latest version and the latest version fixed the bug for you, you no longer need to get help for it.
 |}
 {| class="wikitable" width="100%"
-| Step 4.<br>Exclude any other plugins that are unrelated to the problem.
+| <h2>Step 4.</h2>
 |-
 | This is to ensure that the bug is related to the plugin at hand and not caused by something else.
 |}
 {| class="wikitable" width="100%"
-| Step 5.<br>Recreate the problem for the plugin developer team.<br>MAKE SURE the project works.<br>If it doesn't work due to missing graphical or audio resources, put them in!
+| <h2>Step 5.</h2>
 |-
 | This is to ensure that we are working on YOUR problem and not something else that we might think is your problem. MAKE SURE the bug can be replicated inside the bug report project.
 Also, make sure the project is able to run. We've encountered a LOT of projects that are missing resources needed for it to run, which suggests to us that you didn't test the bug in the project and don't really care enough for it to be fixed.
 |}
 {| class="wikitable" width="100%"
-| Step 6.<br>Write down the steps needed for the plugin developer team to reproduce the problem.
+| <h2>Step 6.</h2>
 |-
 | Just like above, this is to ensure that we are working on the bug that is affect YOUR game project. If there are no instructions on how to replicate the problem, it will not help you get the bug fixed faster. If your bug requires a bunch of steps to get it replicated, and you do not include those steps, do not expect us to figure it out on our own.
 |}
 {| class="wikitable" width="100%"
-| Step 7.<br>Upload the project online to share with the plugin developer team. [[Visustella|VisuStella]] uses Google Drive to check projects.
+| <h2>Step 7.</h2>
 |-
 | Google Drive is the best way to share your project with us. Do not use other online uploaders.
 |}
 {| class="wikitable" width="100%"
-| Step 8.<br>[https://forms.gle/E4aPfWdAf1WSWQnN7 Report it to the plugin developer team.]
+| <h2>Step 8.</h2>
 |-
 | Please fill out everything to the best of your ability.
 |}

@@ Line 40: / Line 40: @@
 This step '''ONLY''' applies to you '''IF''' you are troubleshooting VisuStella MZ plugins.
@@ Line 66: / Line 68: @@
 [[File:Nonnegotiable.png]]
-If you DO NOT have a bug report project attached and all you're sending is just a screenshot, we will not be able to review the bug. Sending the bug report project is non-negotiable. WHY do we need a bug report project? Because it's to ensure that we make sure that the bug we're fixing is YOUR bug using YOUR provided conditions. This is our way of personally working with you on the conditions you've set for the game, bug in a replicated and separated project.
+If you DO NOT have a bug report project attached and all you're sending is just a screenshot or video, we will not be able to review the bug. Sending the bug report project is non-negotiable. WHY do we need a bug report project? Because it's to ensure that we make sure that the bug we're fixing is YOUR bug using YOUR provided conditions. This is our way of personally working with you on the conditions you've set for the game, bug in a replicated and separated project.
-Sending us only a screenshot will result in the bug fix getting delayed and a return e-mail saying that we need a bug report project.
+Sending us only a screenshot or video will result in the bug fix getting delayed and a return e-mail saying that we need a bug report project.