Passive Skill Tree Broken. (Extreme confusion)

[MrKalius]

Guys, what's with the Gates of Fate, how come I'm forced to use Points on nodes that I'll never use in order to unlock different paths, I should be able to unlock if connected anyway? Does it work in a weird way or something? This isn't how it worked in the previous BETA. How does this work, it doesn't seem to be working as intended.

I'd add some images, but steam doesn't exactly allow me to do that on their message boards, so I'll try to explain as best I can?...

Basically, let's say I've got my mage skill tree done all the way to the end (so it connect to the ranged one, for example) It's not allowing me to continue to the second node from there, instead, it's allowing me to continue on the second node in a DIFFERENT place, but NOT to the one I was originally connected too?... If that makes any sense?

Basically, when I finish what I want on the first node and want to continue to the second with the connection, it's not allowing me to do that and instead lighting up a DIFFERENT part of the second node that ISN'T connected to anything RATHER than the nodes that are connected.

I'm being forced to waste points in order to unlock node paths that should unlock ANYWAY, as I've reached the connection bit. This really needs looking into, as I'm unable to play until this is fixed, because I can't get the correct passive skills to continue playing.

I'm having to use points on Melee (something I'd not use, because I'm a ranger) to unlock a secondary Ranged path, DESPITE it being connected to the MAGE path. That makes 0%. I'm sure it's bugged.

I really hope that makes sense.
Thanks guys.

[GODxFIST]

its a bug keep turn the wheel and it will fix itself.

[MrKalius]

Originally posted by BLANKA:

its a bug keep turn the wheel and it will fix itself.

"Rings cannot be moved whilst nodes are pending." So, I can't try that.
"You cannot reach this skill yet." Despite being connected, clearly.
I don't think turning the wheel will fix this. Anyone else I could try?
I've gone ahead and added this to the "Bug Report" section, since it makes the game unplayable and I can't seem to fix it.