[Known] MAX HP BUG STILL EXISTS

7/24/2017 6:04 PM
Title: HP BUG STILL EXISTS
Reproduction Rate: 100%
Blocker? Fixing this requires logging out and logging back in, this happens in every scene, this makes playing the game horrible because it reduces my max hp to 35%

Details:
The maximum hp I am able to get up to is less than the maximum hp shown for my character. My hp is 35% of my max HP at all times on the overworld. I am able to get my hp under 0 and tap soul will not work, and I can't use various other buffs.

Please fix this :-[

Steps to Reproduce:
* Zone into a scene.
* Put on the Ring of Brittle Brawn
* Zone into another scene with the ring on
* Observe your hp is less than max



Observe this screen shot, unable to get more hp than what is shown. I am on the overworld. This happens on every scene

User Specs:
OS: Linux 4.4 LinuxMint 18 64bit
CPU: Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz (8) System RAM: 24021
GPU: GeForce GTX 1080/PCIe/SSE2 GPU RAM: 8192
SotA.EarlyAccess.QA.Linux.64.526.Date.07.24.17
Area: Novia
Area Display Name: Novia
Loc: (446.7, 18.4, -97.3)
Debug: Tm92aWF8fCg0NDYuNjU5LCAxOC40MTYsIC05Ny4yOCl8KDAsIDAuOTgzLCAwLCAwLjE4NCl8MTU4LjgzODd8MHwzNi45OTk5OQ==

 

EDIT/UPDATE: I thought this was the live R43 forums. My mistake. This *is* the DEV plus forums. Fix on QA clearly did not work. We're back to looking at this bug. We also can repro the issue on the internal server which has not yet been published to QA.

Truly sorry for all the frustrations this bug has caused you and others who use it. It's not fun I know as you cannot heal up from it.
@Kigu Starfish (Kor)

 

@Lexie, is this a fix just for this ring or a more general fix for helath bugs that exist?

 

Good question! This particular thread is about the ring. I don't want anyone to lump this thread together with any other health bug issues, please. Then it becomes hard to understand reporting.

 

@oneandonly submitted some fixes that are visible in QA patch 529. Please test and attempt to put your health into a broken state. I want to see if it's really and truly squashed.

 

Still an issue

 

Interesting...

 

@Kigu Starfish (Kor)

TRY NOW! We didn't publish the server report at that time, which would have included the fix.

 

Looks fixed!

 

HUZZAH!