Freelance (Short term) Beta Tester Available + Other

[FeHellX]

Sup! I’m FeHellX (aka Hellparkour on EeveeExpo or Xrasia depending on where you find me).
No need for formalities—I’m not here to scare anyone off. The reason why I put ''Short-Term'' is because I will be going to the University soon in 2 months.

I’m a beta tester by heart (and by habit), usually deep into games—but I also dabble (a lot) in:

• Event handling (Pokémon Essentials structure + the many essentials scripts.)
• Basic coding (Such as creating Abilities/Items/Moves Attributes.)
• Mapping (Layouts/Polish)
• Game balancing

Just passing through for a short-term enrolement, but I’m always down to help or chat if you catch me online.
If you wonder if I have a price tag on my name, you do not dream, I don't have a price tag on myself for the moment.

The only way to assure to contact me 100% is throught Discord : hellparkour (If you use old discord because your device is prehistoric, Hellparkour_#5301)

(Bit of last information : I do want to make a full guide on how Pokemon Essential V20-21 works. But that is only if I have the time for it.)

 

[FeHellX]

I've got asked to provide the way I function because most people would play the game and give an opinion. This is not the way a Beta Tester works entirely.

As a beta tester, I approach Pokémon fangames with a structured and analytical mindset. My process typically follows these key steps:

1. Initial Assessment
   I start by noting the game's current version, changelog (if provided), and any specific instructions from the developers. I analyze the starting flow to assess first impressions, tutorial clarity, and initial game balance.
2. Exploratory Playthrough
   I play the game naturally while documenting bugs, oddities, or inconsistencies. I explore optional areas, attempt to break intended paths, and interact with every object and NPC. I always take note of unusual level gaps, unbalanced trainers, or overly repetitive encounters.
3. Trainer & Level Curve Analysis
   I log every important battle (Gyms, Rivals, Bosses, Major Grunts) and analyze their difficulty relative to the player’s expected level at that point. I also monitor wild Pokémon levels, XP scaling, and availability of useful items or TMs.
4. Event Stress Testing
   I try to trigger events out of order or prematurely to test for softlocks, logic issues, or skipped content. I also check for event clarity and whether players can easily understand the goals and story progression. (I will try to break the game as well.)
5. Mapping & Visual Evaluation
   I examine map quality, tileset consistency, collision bugs, layering issues, and warps. I verify the use of essentials’ tools such as encounter settings, terrain tags, and follower compatibility. (I will not verify it throught the Debug Menu, I will test the terrain tags that are used in the Maps. Essential Tools provides us with this.)
6. Balancing Feedback
   Based on the overall curve, I suggest level adjustments, team reworks, or encounter pacing changes. I compare difficulty between major areas and suggest whether grinding feels fair or excessive. (If there's a Pokédex to follow, I will as well note the Pokédex entirely and adjust by it.)
7. Documentation & Form Completion
   I summarize findings in a standardized document format (e.g., feedback form), listing major bugs, suggestions, level gaps, and personal impressions. I remain constructive and focus on gameplay clarity, balance, and long-term enjoyment,

In total, I will play your game up to 5 times if necessary. The first playthrought will be purely Initial Assessment and Exploratory. Depending of the length of your game, I can't assure you that the time I will give you will be correct. The rest of the playthroughts will be purely to test the strength of the game.


Take note : On July 24th -) July 28th, I will be absent.

Pleased to work with some of you.
- FeHellX

 

[FeHellX]

Bump, I've upgraded the way I will work for Beta Testing.

Instead of contacting me directly on Discord which can now take some times because I will be starting my mastery, I've made up a Form.

Game Information

(To be filled by the developer if needed – describe specific areas to focus on, new systems to test, or known issues to watch out for.)

docs.google.com

The feedback of the game will be directly sent on Discord as usual.

Also, some people asked me if I was doing Event handling Basic coding Mapping as well, the answer's yes, unless I'm too charged.
For those services, you can include them into the Developper's Note.

Pleased to work with some of you.
- FeHellX