 |
when you tried to spawn a ram, did you get any error message? If you remember |
 |
I did get an error message but I do not remember what it was. Roughly a 3 paragraph error message. |
|
|
Sorry, I misread what you type. I did not spawn the ram myself, I dont know if they did get an error message. |
|
|
This is happening once more for destro in Ellyrion. This is the error message they get when spawning a ram. rambug.png (38,595 bytes) |
|
|
as found on discord today I believe that I have just fixed this when addressing another exploit. Im going to leave this ticket up for a while longer (and that other exploit needs to be patched as well ofc) |
|
|
Progressing the zone by the realm ( Whoever killed lord first ) that is not affected by the ram bug, seem to block further progress if the zone affected is a Tier 2 zone and/or maybe also Tier 3 zone. As far as I remember, this did not happen when the bug occured in TM, the campaign progressed properly to Black Crag. When it happened in Shadowland/Ellyrion the campaign could not progress to Averlorn/Saphery. |
|
|
Actually, the campaign progressed to KV since it was bugged on order*. |
|
|
was this before or after todays hotfix? because the hotfix today probably fixes this issue |
|
|
This was before todays hotfix. You are right it probably fixes this issues. Thank you :) |
|
|
Im not a 100% sure but almost certain so im leaving ticket open for now and if a few days passes and I dont hear or see it I will close it. Thanks for the report regardless |
|
|
Although, after restart it seems that the affected zone are bugged and do not progress further, destro just took Ostland and it doesnt progress to Highpass. This might be related to another bug. We will see if it happens with Shadowland as well. |
|
|
Progress on High Elves/Dark Elves campaign is also bugged, people are not getting any crest or renown for kills in Shadowland, this also happened in Ostland, but turning in boxes/capping BOs do give renown. It seems like the pairing is not considered to be properly open. |
|
|
I think this ticket has been resolved since last hotfix, if the issue happens again please reopen or create a new ticket. Thanks for the report. The last 2 comments does not seem to be related to this issue at all but I think those has been fixed as well with the latest hotfix after campaign progressed past them (as they opened in a weird state). |
 |
Fixed in previous patches |
- Anonymous
