Are there any veteran beta testers or game testers who can share methods to assist in finding bugs and exploits? Maybe developers can chime in on things they’re looking for. Regardless of who gets a key everyone should know methods to explore in the game that would help identify issues and help make this a high quality game for everyone. One thing I normally do in games with jumping is trying to jump on objects or through areas should be impossible to get through. Any other tips for everyone would help greatly! Thank you everyone 
7 Likes
Im not a “veteran beta tester”, but the solution is simple: Do stupid stuff no one else does. Thats how you find bugs. Or in other words, play the game!
3 Likes
Good topic, I also want to learn tips about it, I hope there’s some veteran tester that can do this
1 Like
I want to jumping crazy too. I do that in every game you can do that! (・∀・)
2 Likes
what he said lol. i would spam/ chain class skills on areas, or LoS monsters/ bosses behind objects/ terrains etcetc.
Thank very much sir. 
ya, maybe only streamers, youtubers and page managers will get those beta keys.
Lots of ways. Most people focus on one category for one CBT, could be mechanics, dialogue, inventory, etc.
In terms of mechanics, people generally play till mid-game and start experimenting with different skills and equipment to see if the damage calculation is right. Or see if elements and attributes actually work on their respective monsters. These are the theorycrafting people
Dialogue is probably handled by translation team I guess.
The main thing as a CBTester is to simply play the game and be sharp about anything that doesn’t feel right, such as any graphical glitches, any area which u can get stuck on, skills not working as intended, movement and animation of sprites, inventory problems, etc etc. Then submit a bug report and see if there’s any response. If there isn’t, then it’s probably how the game is supposed to be.
Things to note is that you should know as much information as possible about the previous CBT so that you don’t repeat the same problems as everyone else. There could also be in game notices by IMCgames for people to look out for particular spots or areas where bugs are very common.
2 Likes
mostly not all.
i dont know how imc is going to give the keys.
Some people might try to grind through the game and miss some stuff. I do agree we need to do the stupid (and fun imo) stuff. Are there any things you do that you consider out of the norm? Any methods helps everyone get some ideas =D
I think that trying differents combinations of skills is a good way.
Go where no one else goes. -> Go into corners and see if you get stuck, clipping issues, etc.
Use skills (and their combinations) no one else uses, preferable on as many occasions. For example, using the dievdirbys silencing skill on a monster that is about to cast a spell, maybe he gets stuck eternally in his casting animation, etc.
Hug every walls or any obstacle in the middle of the road, crash into them from various angle by jumping or not several time.
Become the walls.
try the new features and see if they are working properly. most of the time new features are bugged.
Play the game, got crash, bug, glitches, report to developer. Be good tester, always give a positive feedback, not complain the dev just because they are a little bit sloppy or slow fixing stuff… The dev team are human too. And follow the beta test rules.
Reporting bugs is for nerds. I’m just going to break things and make sure none of you have a good time.
2 Likes
Usually in game testing, Devs will give to QA a list of features, and they have to test every bit of it, with a Checklist.
First things to test are:
Stability - Memory, Stress Test.
Input - Key Responsiveness, Navigation, Function
Level Design - Spawn rate, Collision, ect.
But these already likely happened in internal test, along with other features. So if you find one, it’s usually a minor issue (given IMC QA did their work good)
The important thing in CBT testing is the number of testers. They should play the game as normal user, to cover more ground. 1 feature alone likely won’t have any bug. But when you interact 1 feature with 1 or more features, bug will likely happen as the steps to reproduce bug is complicate that IMC QA didn’t had chance to explore.
Yeah, the idea of doing things that no one do is basically right, but it already be covered by QA.
What they couldn’t cover is for example…an account with 100+ friends, a raid party with full member of 30, etc. That’s where they need us.
1 Like
Hello,
I think if you do what everything in game, you will found some weird things, test it before u caem around saing " i found a bug "
I’ve beta and alpha’d a few games over the years… some general tips are:
- be prepared to remake your character so you can try out all the skills
- look at item/skill/dialogue descriptions & boxes to check for errors talk to npcs to make sure something wonky in their dialogue/coding doesn’t cause you to crash
- try out different graphics settings
- try to be friendly even when people ask silly questions in game
- explore areas on the map, try to get bugged out on the map or into areas you shouldn’t be able to
- watch out for monster’s skills and see if there’s something off with their skills/text (if they have any) ect
- make sure your items descriptions (armor/potions) fits the effects/stats you actually get when you use them
- don’t get upset if there’s a lot of downtime while things are hotfixed
- make sure to communicate with other players about things, and ask questions
- use the search function to see if there is already a report or thread about your error–add to that thread instead of making a new one (this is a big one, esp to help the devs and make their job easier so that they don’t have to sift through 100 repeats of the same error in different posts)
- when you report a bug, include as much information about what happened as you can
i.e. Instead of “hp potion don’t work” something like “When I used XXX potion on my XXX class character it didn’t blah blah blah when the description said it should blah blah blah” and include a screenshot if you can.
2 Likes
You just play the game as usual, preferably with a video program such as OBS or Shadowplay running in the background so you can record the last 10 or so minutes from when you encountered a bug.
If you happen to find a bug, make a youtube video showing it in detail and post it on forums kinda like: Halo of Arlyse minor bug
If it’s a problem with text simply screenshot it and highlight/zoom in on the incorrect text.