Community Manager[GUIDE] How to Report a Bug & Find your Player ID in Plants vs Zombies 3
Welcome to the topic dedicated to reporting bugs & finding your player ID in PvZ 3.
Are you experiencing issues with Plants vs. Zombies™ 3? This guide will assist you in navigating the process of finding your player ID, collecting the necessary information, and filling out the Bug Report template for PvZ 3.
WHERE TO FIND YOUR PLAYER ID IN PLANTS VS ZOMBIES 3
While you don't always need to give your Player ID when you report a bug or other technical issue with the game, it's good to know where it is. You can find your PvZ 3 Player ID by following these steps:
- Open the Settings menu from your home screen.
- You’ll see your Player ID at the bottom of the screen.
For images, please click on 'Spoiler':
- Open the Settings menu from your home screen.
- You’ll see your Player ID at the bottom of the screen.
CREATING EFFECTIVE BUG REPORTS & USING THE TEMPLATE
Make sure the thread title summarises your issue
Thread titles play a critical role in identifying your issue, so ensure they are clear, concise, and accurately summarise your problem. For instance:
• 
'Zombies stop spawning while collecting suns since recent Feb. 24 update' <--- Precise, concise, clearly portrays the problem
• 
'WHY IS MY GAME NOT WORKING??!! PLEASE FIX!!' <--- Unclear about the problem
Clear thread titles help sort out problems faster and are helpful for the teams fixing the issue.
GUIDELINES FOR BUG REPORTING
Filling out a bug report template with detailed responses is important. Don't copy and paste the same answer into all the fields. Instead, take time to provide thorough information for each question. Each question is there for a reason and the more specific you can be, the better.
Provide extensive information wherever possible
The bug report template will ask for basic details, but giving extra information can help us a lot. You can include any error messages or codes, things you've tried to solve the issue, or even pictures or videos. The more complete the information, the easier it will be for us to find and fix the problem.
Restrict bug reports to one issue per report
Lastly, when submitting bug reports, stick to one issue per report. It might seem like extra work, but it helps us see patterns and track issues more effectively. It also avoids confusion and can speed up the problem-solving process.
Here's a visual of our current Bug Report Template for PvZ 3 (please click on 'Spoiler'):
Tip! If you want to include screenshots in your report, it is recommended to upload these straight to Answers HQ. This is because there's a chance images might get deleted on some third-party websites. You have two alternatives for adding images:
- Click on the picture icon in the toolbar and proceed to upload it.
or - Choose the 'Attach file' option at the bottom.
Please click on 'Spoiler' to view image:
HELP! THE TEMPLATE DOESN'T LOAD OR I GET AN ERROR WHEN TRYING TO POST!
Should you encounter difficulties in submitting your bug report, ensure that you complete the final section of the bug report form. Also, remember to include any additional information that you might have overlooked.
If you're unable to complete the bug report template, the following information would be very helpful to the teams:
- Platform:
(iOS or Android) - What's your device's make and model?:
(Example: Apple iPhone 15, Samsung Galaxy 24) - What version of operating system are you using?:
(Example: iOS 17.3.1, Android 14) - Where did the issue occur? Please include menu name or in-game location.:
- What kind of issue do you have?:
(Example: Gameplay, Text, Crash) - What happens when the bug occurs?:
- What do you expect to see?:
- Steps: How can we find the bug ourselves?:
WHAT'S THE NEXT STEP?
Our team will look into your report and we may get back to you. If the report is valid, we'll mark it as a new issue and let the game developers know. We might also need more information to understand your issue better. If the issue has been reported before, we'll tell you.
IMPORTANT: Sometimes, reports are closed because we can't reproduce the issue. This can happen for many reasons. It doesn't mean your report was wrong, it just means we couldn't see the issue ourselves.
After we flag your report, there's a possibility we'll close your thread or report. This doesn't mean your issue is fixed. It just means we've told the Dev team about it and they're looking into it.
