The ENTIRE Skill tree system needs to be completely redone. Over 40% of interactions don't work/broken, 70% Useless. (Rant warning, I quit, this game will be at ~100 players in 8 months))

[Psojed]

@Llama8

My egregious typos aside (damned phone keyboard), all skill nodes needs to be functional at all number of points (sometimes the first point works, sometimes that’s the only one that does), not just the ones that “every player who has a single neuron in their head will select” (thanks for denigrating anyone that isn’t a meta-slave, classy!). Things (including skills) need to work over the levelling process/early game, not just at the end game with maxced out/BiS gear.

I believe that Kiwitus said “beta test all of the skills and their interactions”, which includes testing skills at 1/X points invested.

As for “things”, they are not something you will test on a regular basis, because unlike skills, they’re not changing leveling process nearly every patch. IIRC we had leveling bugs on release and we still have them today as indicated by 1.1.7.2 Patch Notes, so it’s not as if their QA did a great job on leveling tests either.

@Llama8

Except you’ve just said that you don’t know anything about testing, nor does your bf because apparently their software never has any bugs, so by your own admission you don’t know how much time it takes per skill/node. Having done testing before & had to write up useable bug reports (not just “X doesn’t work, pls fix k thx bai”), it takes a lot longer than you’re thinking. Especially the documentation bit so that the programmers can have a better idea of what’s going on versus what should be goinb on in the code.

You’re assuming a lot here.

The scale was absolutely blown out of proportions, we even got a “thousands of interactions” comment in here.

Not sure what testing you did, but in case of many skills it would absolutely take minutes tops. For example, a skill passive with effect “X% of attribute gained as Ward per cast”, your bug report would literally be

Skill name - Passive name

Passive X doesn’t give the correct amount of Ward. It gives Y, should give Z.
Attached:
2 screenshots OR log (if even required)

And writing a bug report definitely doesn’t take long. With proper testing environment, documentation is as simple as two clicks. Without it, manual log search is minutes tops. Not to mention you don’t always need it. Contrary to your experienced belief, sometimes just saying “X doesn’t work” really is enough.

And in case it matters, I do have QA testing experience.