Naero

An official PRO Wiki Discord is now live—an outreach I felt the resource was long-overdue for. Communication is the lifeblood behind such a collaborative resource; and although communicatory mediums have existed prior, most were found to be either too disjunctive, such as DMs; too fringe for the average usership, such the wiki's own intraforums; or overformal, as many might feel about these very forums for such discussions. Each medium has its own purpose, but none have optimality as all-encompassing as the Discord-server. With the advent of PRO Wiki Discord, there's now a much better-tailored platform to post about everything within the wiki's ambit: technical support, feedback, error-reporting, and collaboration. Feel free to join it via the invitational link (infra), and feel even freer to use it to synergize with fellow editors or otherwise readerly contributors. Join the PRO Wiki Discord here!

Thank you very much for the meticulous testwork and formulaic emendations, Kaminokage; I should re-upload the drawing board onto the wiki, momentarily. :) I had second-guessedly figured that the bonus-experience perks stacked additively, not multiplicatively; however, due to lacking the wherewithal (guild involvement) for effective testability and other priorities at the time, I had adjourned it but had only just remembered it when you raised it up. As for the base-experience discrepancies: that would be informatively helpful! They have not misinformatively impacted any of the leveling charts I've generated for Pokemon pages so far, as I do try to do confirmatory checks to ensure that the experience chart is concordant to the base value, but this information would be very helpful for correcting all the misassigned values that might still exist in the wiki's Pokemon CSV. Since PRO's Pokemon database was imported in accordance to Generation IV data and has not been updated since, though, all base-experience values should align to their Generation VI values or primordial ones for any post-generational Pokemon.

Hello. Due to the inapposite disappearance of a different, non-boss iteration of George, that step currently is not progressible; as such, the only workaround, meanwhile, is for us to manually amend your quest variables in-game so that you can proceedingly complete this step. Please post on the #support channel of the aforementioned Discord to solicit our attention whenever you're around; that way, we can coordinate a time to log in-game simultaneously and ultimately fix your user variables. Apologies for any inconveniences, meanwhile.

Hello. :) Firstly, I should reaffirm the fact that none of the bells are rewardable from George; the boss-NPC iteration of his is not tied to the quest, and you can see the entire gamut of his rewards here: https://prowiki.info/index.php?title=George_(boss) Now, more germane to your issue: there was a non-boss counterpart of George that would progressively register your variables; that version has inexplicably disappeared, meaning that step is currently not progressible. We will look to reinstate this NPC with due course; but for the here and now, and the only stopgap solution is for us to manually register your user variable concordantly so that you can proceedingly complete the next step. We will need to log in concurrently for your variable to be fixably registrable; therefore, we would enjoin you to post either here or the #support channel on PRO's official Discord to solicit our assistance whenever you're able to log in-game so that we can amend your quest variables. Thank you for your patience, and apologies for any inconveniences impinged by this, meanwhile.

Hello, and thank you for reporting this inaccessibility. :) Apologies on behalf of the staff. When stationing in this move-tutor on Silph Co.'s second floor, we were not fully cognizant that its accessibility would have been precluded by the postliminary control-flow changes of completing the quest; therefore, we failed to ensure its accessibility's continuity. This has been rectified, however, as the NPC has been transposed to Silph Co.'s lobby, thereby accessibilizing it to those who have completed the quest. Thank you again for raising this up, and apologies for any inconveniences caused, heretofore. :)

I've correctively emended the Pokedex data used in the Pokemon-cry function's argument. Thank you for reporting it. :)

Hello. :) Thank you for reporting what you believe to be a bug, but I can confirm that there is no control-flow disorder with the quest-work; rather, there are incompletions on your part. As I educed from your user variables, you already defeated Novi; that is why she is irreversibly invisible, because these battle-NPC constituents of the quest are only invisiblized when they are defeated. Rest assured, there is no cooldown-time deadlock on your end; but for what it is worth, I shall correct another misconception by informing you that all cooldown-time durations of these NPCs are for 2 hours, not for two weeks as you may have initially misbelieved. Your journey to Sinnoh is still progressible; you just need to know where to progress next, as there are still more quest-compulsory battle NPCs to defeat on your end. According to the incremental variable used to count this, you already defeated 4 of them out of 6 total; I would peruse through the quest-guide topic to help ascertain which ones are still awaiting you. Apologies for any misconceptions that may have arisen from our explanations of the quest, and good luck completing it!

Hello, and thank you for your report. :) I have changed his sprite to the one most associably used for all Youngster Joey iterations. While he is intended to tag along as a Team Rocket Grunt, indeed, it was not realistic for him to don the outfit, concordant to the dialogue, so I have changed the sprite.

Hello, and thank you for reporting this. Fairy Wind is not database-mapped into the moves partition of the database; this is why it did not effectuate in your Togekiss' moveset during the resultless transactions. We were not cognizant of its inexistence in the database at the juncture that these move-inheritors were scripted, so it was an oversight on our part that we apologize for. Unfortunately, the lost payments are not compensable due to various ethical and technical complicators, but we have done a systemic fix by removing this move and adding in Magical Leaf in its vacancy; as such, it should not recur. Apologies for the misguidance caused by this move's erroneous addition on the move-tutor, and thank you for reporting this.

Hello, and thank you for the report. :) Apologies for any inconveniences caused by this blip. While you do seem to understand that Nikola's rechallengeability is not compensable, I do want to pledge assurance that these blips will not be recurrent moving into the future, as I have fixed it systemically. There were multiple omissions on our part that have possibilized this; I will note them below. Firstly, I have added a confirmatory prompt on Nikola's dialogue, meaning that he will ask you to confirm your readiness for challenging you before proceedingly initializing the battle; this allows you to ascertain Nikola's availability by speaking to him without any initiability on the battle script's part. Secondly and lastly, if you wish to do more than a binary check on Nikola's readiness, you can now do a quantitative check by speaking to any of the all-encompassing cooldown-timers available, as I have just incorporated Nikola's timer into the check. Because the domain of his boss post (Trainer's Valley) is categorized as an expansionary area to Kanto, I have subsumed his check under all Kanto checks—for those that need that referential pointer. Apologies again for any inconveniences this has caused on you, and I thank you on behalf of the staff for understanding and dutifully reporting this.

There are four computational storages total; you might not have checked the one on the B3F floor, which is the one outlier from all the ones you checked on Giovanni's floor. Check it, and it should be readily retrievable for you to finalize the quest. Let us know if difficulties persist, otherwise. :)

Hello, and thank you for dutifully reporting this. :) While I have amended the gym's scriptwork to preclude any recurrence of this deadlock, those who are still beset by it will need to be manually extricated; if that is the case with anyone else, please post in General Support, accordingly. Apologies for any inconveniences caused by this, and thank you again for the report.

Hello, Aladdin, and thank you for registering your interest in contributing to PRO Wiki. :) Firstly, if you have not already filed an account request, I would enjoin you to do so here; thereafter, I can activate your account to operationalize your usership. Since you have narrowed down the field to your primary contributory interest in the wiki, I shall give you some pointers and protips in that regard. The paradigm of wiki-editing is easily learnable overall, but it still entails a learning curve; one of the best vehicles for traversing that is by reverse-engineering the pages, which is why I would advise reading the source codes of various locational pages in order to best have a cryptographic understanding on the nuts and bolts of creating these pages. On the source codes, you can see the various modular templates used to construct these pages—much of which require minimal input to display on the pages and already have data, such as all Pokemon spawns, already in the wings; ensure that you add all of them on the area pages where applicable on the pages that you wish to create. It isn't an epistemicide if you initially omit some of this information, but do try to ensure that you at least add in all the cardinal essentials of it—Pokemon-spawn data, the information box, and so forth. Lastly, if you have any clarificatory questions needed in editing these pages, feel free to contact me on whichever medium you find optimal. Thank you once again, and happy editing. :)

Hello. From what I've educed out of your item and user-variable data, it appears that you've initially obtained the Water Bell but bequeathed it to Assistant Davis in exchange for the Zap Bell; that is why you do not have the Water Bell in your possession anymore. Assistant Davis is calculatively designed for those initially mis-selected the bell and want to reselect it for the homologous Pokemon that they want to encounter; therefore, it is only a one-off swapover with no do-overs, I'm afraid.

Hello, and thank you for dutifully reporting what you inferred to be a bug, but I can disconfirm it; it is working as intended. If Pikachu is your starter-Pokémon selectee, the boss in question will not stipulate that it must be on-hand in order for it to be challengable; you only need to be registered as a Pikachu-starter, which is discernible to scripts without its insertion in your on-hand lineup. This is a similar parameter employed for other clausal perks of starting with the Electric-type starter, such as its individualized Surf-tutor; because an identificatory variable is registered to your account in unison with selecting your starter Pokemon, the scripts can ascertain that you started with Pikachu by reading that variable, thereby denecessitating the Pokémon-selector prompt. Topic locked, as there is no aberration, here. :)