 |
A little more testing, if I leave the war camp as a 41 it will eventually change me back to a 34, but the flip flopped bolster remains. If I go back through the war camp into RVR, it still won't bolster me to 41 until I leave RVR |
|
|
Another note, it seems if I go to another place it will bolster me. For example, I was having the issue in KV, where I wasn't being bolstered when I left the war camp. When I got to Karaz Drengi, and the screen said I was there, it bolstered me up to at that time. It didn't when I went to Hardwater Falls. |
|
|
Confirmed this, bolster is almost acting like a toggle, and it easily gets in a state where the situations it should apply in are reversed, bolstering in the warcamp and not in the lake. Leaving the warcamp into PvE debolsters you and seems to fix it temporarily. Also confirmed with getstats that this is not just a visual bug, my poor lvl 18 is really running around in T4 RvR with 2k health :(. |
|
|
I first notived this today in praag, it was fine when I relogged, but then as soon as I died it went back to bolstering me only in the warcamp but not in the rvr zone. Has the same characteristics as listed above with R1CH |
|
|
I have managed to inflict this on myself and decided to record it for better understanding for devs. Video link here https://www.youtube.com/watch?v=8nOQ-Ad4Dk4 Freshly made character, got 3 kills with AAO and got to level 4/7Renown. I ran back into WC to equip some low level gear, do the renown quest, bought some basic renown gear and went back into the lake. The image also shows a full combat log of me dying in about 2-3 seconds as I had 1k hp and no bolster so it isnt a visual bug. |
|
|
I have now managed to recreate this twice. I ranked up to 5 and 6, killed myself by running into enemy. After I respawn the bug in the video persists again until moving zone. https://www.youtube.com/watch?v=20b0k-cKkls Prior to this video all I did was get 4-5 kills, die and respawn as a new level |
 |
Im hesitant to close this ticket just yet but we think its been fixed with the hotfix this morning (from my experience today it seems to be fixed at least) |
|
|
This should be fixed now. If its not please open a new ticket or reopen this one. |
- Anonymous
