- Joined
- Mar 11, 2025
- Posts
- 1
Overview of the Project
We are working on updating the VS Seeker Plus script, originally created by KleinStudio (Discord: Klein#3860), to make it a more modern and robust plugin for Pokémon Essentials. The current version we are building is compatible with Pokémon Essentials v20.1, with the goal of eventually expanding compatibility to v21. This work is being done collaboratively by me, elios92, with the help of GitHub Copilot.The key feature of this plugin is to provide a trainer rematch system that works seamlessly and efficiently. The idea is to allow trainers to re-challenge the player after a certain condition is met (e.g., using the VS Seeker). This includes transitions between event states to properly manage rematch availability.
What We Have Done So Far
- Adapted the Original Script:
- We took the original VS Seeker Plus script by KleinStudio as a base and started updating its logic to fit the current needs.
- Implemented Event Page Management:
- Added functionality to handle transitions between Page 2 (Trainer Defeated) and Page 3 (Rematch Available) based on custom Self Switches (<span>A</span> and <span>Vsseeker</span>).
- Introduced Debugging Information:
- Added debug logs to monitor the state of Self Switches (<span>A</span> and <span>Vsseeker</span>) before and after battles, ensuring we can trace issues easily.
- Created a Script to Trigger Rematches:
- Wrote a script (<span>activate_vsseeker</span>) to enable rematches by setting <span>Vsseeker</span> to <span>true</span> for applicable trainers.
- Ensured Map Refreshing:
- Incorporated <span>$game_map.need_refresh</span> calls to ensure the map state updates correctly after changes in Self Switches.
Current Problems
Despite the progress, we are encountering a few issues:- Stuck on Page 3 (Rematch Available):
- After the rematch ends, the event doesn't always transition back to Page 2 (Trainer Defeated) as expected. This seems to be related to the handling of <span>self_switch("Vsseeker", </span><span>false)</span>.
- Self Switch Behavior:
- In some cases, the <span>Vsseeker</span> Self Switch doesn’t consistently trigger the expected behavior, even when the debug logs show it has been set correctly.
- Compatibility with Future Versions:
- While the current implementation works with v20.1, it’s unclear whether this logic will remain compatible with v21 or future versions of Pokémon Essentials.
- Event Refresh Issues:
- Even with <span>$game_map.need_refresh</span>, the event graphics or behavior sometimes fail to update in real time, leading to inconsistencies in the user experience.
Next Steps
- Fix Transition Logic:
- Investigate why the transition back to Page 2 doesn’t happen consistently after rematches and ensure the <span>Vsseeker</span> Self Switch is reset properly.
- Test Compatibility:
- Continue testing the plugin on v20.1 and start preparing for potential adjustments needed for v21 compatibility.
- Community Feedback:
- Share the current progress on forums (e.g., GitHub Discussions, Relic Castle) and ask for input or collaboration from other developers familiar with Pokémon Essentials.
- Enhance Debugging Tools:
- Add more detailed debug output to pinpoint when and where the event logic fails, particularly around Self Switch handling.
Summary
This project aims to modernize and improve the VS Seeker Plus script by turning it into a robust plugin for Pokémon Essentials. While we’ve made significant progress in adapting and updating the script, there are still challenges with event transitions, Self Switch behavior, and compatibility with future versions. We welcome feedback and collaboration to help refine the system further.Let me know if you’d like to adjust or expand any part of this explanation!

Description of the Issue
We are currently working on updating the VS Seeker Plus script (originally created by KleinStudio) to modernize it and add new features as a plugin for Pokémon Essentials. The current version is made compatible with v20.1, and we aim to ensure future compatibility with v21. However, we are facing some challenges with event page transitions and Self Switch management.
The Current Problem
- Transition Issues:
- After the player completes a rematch, the event does not always transition back from Page 3 (Rematch Available) to Page 2 (Trainer Defeated) as intended. This leaves the trainer stuck in the rematch state.
- Self Switch Behavior:
- Debug logs show that the <span>Vsseeker</span> Self Switch is being set correctly, but the event does not consistently reflect this change in its behavior.
- Event Refresh:
- Despite calling <span>$game_map.need_refresh</span>, the events sometimes fail to visually or functionally update their state in real-time.
What We Have Tried
- Debugging the state of Self Switches (<span>A</span> and <span>Vsseeker</span>) before and after every battle.
- Ensuring that <span>$game_map.need_refresh</span> is called after every change to Self Switches.
- Verifying that trainer event names follow the expected format (e.g., starting with "Trainer").
Request for Help
We are looking for assistance in resolving the following:
- How to ensure smooth transitions between event pages (specifically from Page 3 back to Page 2) after rematches.
- Any insights into why <span>$game_map.need_refresh</span> might not always work as expected.
- Tips or best practices for managing Self Switches in Pokémon Essentials, especially when handling multiple conditions.
If anyone has experience with similar issues or knows how to address these problems, your help would be greatly appreciated!
Last edited by a moderator: