Shiningluck

You're familiar with the previous exp system, that's why the current one looks strange to you. I will just focus on your main point of "Low experience bug" report, and can confirm it's not a bug at all following the updated exp system. In the original game, you would have received a bit less than that (rounding issue) --> https://streamable.com/pkkol2

Hello @Rraden, Thank you for taking the time to report the issue. Though the exp received seems to be lower than the previous state (before the exp rework update), it is actually the correct amount you should be receiving following the exp gain formula applied in gen 7th of the original Pokemon game. For your information, in the original game, with the described situation, you would have received 731 exp, the difference is small due to rounding issues. Thanks again for your report, and feel free to send us anything you consider buggy in the future. Have a good day. Regards, Shiningluck

Hello, @Mdatt Thank you for taking the time to report the issue. I checked all 4 regions Safari's NPCs and there was no bug within. However, there is a possibility for the described issue to have happened, that's when you leave prematurely and re-enter the check gate (the 2 guards blocking) for 4 more times, leaving the area before its end-time will end your session immediately (no matter how many time remains), entering it again after that will cost you the price for a new session. Could it possibly be the actual situation? Looking forward to your response. Regards, Shiningluck

Hello, @Xmonts Thank you for taking the time to report the issue. My apologies for any inconvenience it may have caused. Our Dev has looked into the case and applied a fix for it, though it might take some time for the fix to be updated on the live server. Please kindly let me know if you ever run into it again. Thanks again for your report, and feel free to send us anything you consider buggy in the future. Have a good day. Regards, Shiningluck

Hello, @Excelso Thank you for taking the time to report the issue. Your case is checked and it appears that there is no bug within, both sides Mega-Lopunny reached max speed in fact, yours lost the speed tie against him, which explains why his Mega-Lopunny went first. Though you mentioned of seeing a 28-speed Lopunny, that was definitely not the actual Lopunny you fought against in that battle. Thanks again for your report, and feel free to send us anything you consider buggy in the future. Have a good day. Regards, Shiningluck

Hello, @Vns44 and @Pity Thank you for taking time reporting the issue to us. My apologies for any inconvenience it may have caused. Our CS has looked into the case and applied a fix for this issue, it shouldn't occur anymore, but in case it re-appears somehow, please kindly let me know. Thanks again for you guys report, and feel free to send us anything you consider buggy in the future. Have a good day. Regards, Shiningluck

Hello, @Ozzymate Thank you for taking time reporting the issue to us. My apologies for any inconvenience it may have caused. This issue has been forwarded to our Artist team, hopefully, it will get updated soon. Thanks again for your report, and feel free to send us anything you consider buggy in the future. Have a good day. Regards, Shiningluck

Hello, @Apocalypse Thank you for taking time reporting the issue to us. My apologies for any inconvenience it may have caused. You've encountered a known bug of the Fishing Contest. Luckily, you can fix it by interacting with NPC Expert Fisherman on Corsica Island while the Fishing Contest is not ongoing. So, you still have around less than 60 hours in this week to do so (before the contest starts). With that, you'll be able to join the Fishing Contest again when it starts. Thanks again for your report, and feel free to send us anything you consider buggy in the future. Have a good day. Regards, Shiningluck

Hello, thank you for your report. Your PvE coins should be updated after relogging. I hope this can clear up your doubt. Thanks again, feel free to report any bug you found in the future. Have a good day! Regards, Shiningluck

Hello @Tezkatlipoka The case is still under investigation and will be notified to you right when it's solved. Could be I was still missing some steps to replicate it, please clarify some more questions below to help with the investigation: 1/ How many player joined that dungeon run? (2 were reported for item missing, what about other member of the team, if any?) 2/ If there're more than 2 players joined the run, can you tell me what you can remember about the situation of each member the moment the "unexpected error" message popped up when trying to escape the Reward Room to the South (anyone of you got wiped out - all team fainted?) 3/ Even with the said "unexpected error", you guy were still able to escape the dungeon to the Forlorn Court without the help of any staff? (as some players reported to be stuck in the Reward Room & couln't leave the room when that error message popped up). 4/ From this part: It seems that you guys decided to start another new run (let's say it's the 2nd run) right after the mentioned bugged run (the 1st run), went through the entrance but went out to end the run immediately? Then the screenshots you provided (in map Forlorn Court) were from after the first run, or 2nd run?

Hello @Tezkatlipoka Thank you for taking time reporting the issue to us. My apologies for any inconvenience it may have caused. Please provide some more information below to help with the investigation process: 1. What is (are) the player(s) that got the same issue described above? (use the template below) - Player name: - Server: 2. How did you guy leave the dungeon? Did you finish the adventure and leave from the Reward Room, or had to forfeit the run due to being wiped out (full team fainted) and left from map Forlorn Foyer (the first map when you enter the dungeon entrance), or left the dungeon with a different way? I'm looking forward to your reply. Thank you. Shiningluck

Hello, @Dubbledii Thank you for taking time reporting the issue to us. My apologies for any inconvenience it may have caused. Your findings were partially correct, Tail Slap is using the description of Trop Kick instead of it own. As for the number of strike, it works correctly as of now, you were probably reveiced a low roll on the number of strike at the time you tested. I have forwarded the issue to our Devs. And hopefully, it may get fixed soon. Thanks again for you report, and feel free to send us anything you consider buggy in the future. Have a good day. Regards, Shiningluck

Hello, @Darioymateo & @Godfrezy Thank you for taking time reporting the issue to us. My apologies for any inconvenience it may have caused. From my observation, a bug occured by a certain interaction during the battle that lead to the described stucking situation. Moderation Staff has been notified of the case, and will probably reach up to both of you at their soonest convenience for a solution to the stucking situation and the respective rating of both sides after battle. As for now, please offer your help with our investigation to clarify the bug better, by answering/ providing evidences (screenshots) for the following questions (if possible): 1. On the turn right before the stuck, which was the action chosen by each side? (Which pokemon facing each other, which move did they use?) 2. On the turn the stuck happened, which was the action chosen by each side? (Which pokemon facing each other, which move did they use?) I'm looking forward to you guys respond. Thank you. Shiningluck

Hello, @Elnaaz Thank you for taking time reporting the issue to us. "Role Play fails if the target has the same Ability as the user" (quoted Bulbapedia). In this case, your Alakazam and the wild Natu share the same ability (Synchronize). That explains the fail of Role Play. Hope this clears up your doubt. Thanks again for your report, and feel free to send us anything you consider buggy in the future. Have a good day. Regards, Shiningluck

Hello, @Animesh3011 Thank you for taking time reporting the issue to us. However, Mirror Move is currently not coded, so it has no effect in copying the nearest move targeted at it, that explained the Z-Mirror Move you tested could only raise the ATK stat by 2 stages and had no other effect. Thanks again for your report, and feel free to send us anything you consider buggy in the future. Have a good day. Regards, Shiningluck

Hello, @Phanikumar Thank you for taking time reporting the issue to us. My apologies for any inconvenience it may have caused. Your findings were correct, it's a visual bug in the enemy team preview panel of not showing the correct fainting status when a Pokemon used a self-fainting move. The issue is known to our Devs and will be fixed in the next client update. Thanks again for your report, and feel free to send us anything you consider buggy in the future. Have a good day. Regards, Shiningluck

Hello @Mprokolo, thank you for taking time reporting the issue to us. I've just checked into it and the Pick Axe is working correctly. When it's already in your bag, you only need to make your character facing a break-able rock and interact with it (button Z by default). Clicking on the Pick Axe in the bag or press it in the hotkey bar is not the correct way to use, it doesn't require TM Rocks smash either. Hope this solves your issue, and feel free to send us anything you consider buggy in the future. Have a good day. Regards, Shiningluck

Hello, @Masskiller Thank you for taking time reporting the issue to us. My apologies for any inconvenience it may have caused. Your findings were correct. It's a wrong Sitrus berry consumed message that appears when a Pokemon holding Sitrus berry and is behind a substitute got it Substitute destroyed by an opposing multi-strike move, even if the HP condition for the Sitrus berry to be consumed hasn't been met. However, it's just a wrong message, the Sitrus berry didn't actually get consumed at the first message, and the second message of consuming the Sitrus berry was correct. So, this won't affect the outcome of that turn. I have forwarded the issue to our Devs. And hopefully, it may get fixed soon. Thanks again for your report, and feel free to send us anything you consider buggy in the future. Have a good day. Regards, Shiningluck

Hello, @Henr1que Thank you for taking time reporting the issue to us. I tried to reproduce the same situation mentioned above with ranked PvP rules applied, and the Sleep Clause works fine. Could it be that this was from your friendly-battle with Phanikumar, where ranked PvP rules didn't apply? To apply ranked PvP rules in a friendly-battle outside of ranked queue, you can use this command: /battle [playername], true Hope this clears up your doubt, feel free to add any info on this should you remember something. Thanks again for your report , and feel free to send us anything you consider buggy in the future. Have a good day. Regards, Shiningluck

Hello @The1banned, Thank you for taking time reporting the issue to us. My apologies for any inconvenience it may have caused. Your findings were correct, currently, Keldeo-resolute form exp. bar got reset upon: - Equipping/ removing its held item - Teaching it a new move I have forwarded the issue to our Devs. And hopefully, it may get fixed soon. For the time being, please avoid actions listed above to soft-fix it before it got completely fixed by our Devs. Thanks again for your report, and feel free to send us anything you consider buggy in the future. Have a good day. Regards, Shiningluck

Hello, @Phanikumar Thank you for taking time reporting the issue to us. Repel prevents wild pokemon with a lower level than the first member of your party from appearing. Because the first member of your party was at level 28, repels couldn't help you prevent wild Pokemon with higher level than that from appearing (the level range of the wild pokemon in Dragons Den is from lvl. 50-54). If you want to prevent all wild pokemon in this map from appearing, make sure the first member of your party is at level 55 and above. Hope this clears up your doubt. Feel free to send us anything you consider buggy in the future. Have a good day. Regards, Shiningluck

Hello, @Pokemonrh Thank you for taking time reporting the issue to us. My apologies for any inconvenience it may have caused. The message should appear only when there's entry hazards exist on the field. I have forwarded the issue to our Devs. And hopefully, it may get fixed soon. Thanks again for your report, and feel free to send us anything you consider buggy in the future. Have a good day. Regards, Shiningluck

Hello @Acetzy, Thank you for taking time reporting the issue to us. Starting from Generation 3 onward, "a frozen Pokemon has 20% chance of being thawed out each time it attempts to move" (Bulbapedia) This status doesn't have a counter like the Sleep status, so everytime you try to click a move with your frozen Pokemon, the 20% odd to be thawed out applies, switching out does not help in this case, also. So the situation you reported was possible to be occured and the status is working correctly as intended. To get a frozen Pokemon to be thawed out, you can make use of the following move: some damaging Fire-type moves, Hidden Power Fire, Scald Hope this clears up your doubt, feel free to send us anything you considered buggy in the future and have a good day. Regards, Shiningluck

Hello, @Sweatyabdus Thank you for your report. I re-checked both NPC PVE Coin Apprentice (Silph Co. 1F - Saffron City) & PVE Coin Master (Celadon Mart 4). The option to spawn syncable pokemon from both NPC is working correctly as of currently, clicking "no" when you were asked "are you ready for battle?" will only help you quit the conversation with him, without spawning any unwanted syncable pokemon or consuming your PVE coin as described. If you can provide video evidence of the mentioned issue, it will be more helpful for us to investigate further. Please notify me when you have new evidence of this. Have a good day. Regards, Shiningluck

It was from yesterday, August, 15th, is that correct?