View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0021008 | Return of Reckoning | General | public | 2023-08-23 20:14 | 2023-08-24 07:42 |
Reporter | Rapzel | Assigned To | MaxHayman | ||
Priority | normal | Severity | major | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Summary | 0021008: NPC and stationary siege equipment keeps respawning | ||||
Description | There should exist one siege merchant, one cannon at each location in a defense tower. Currently they keep respawning allowing the defender infinite number of siege merchants and keep cannons. | ||||
Steps To Reproduce | Get 2 star keep and wait | ||||
Tags | No tags attached. | ||||
do they spawn infinitely or does one need to be killed? | |
There exists more than one on all of the locations. Easiest to see when you look at the Siege Weapon Merchant as the model keeps changing there. more pictures added from different locations. The single target cannons don't seem to suffer as badly, but may be due to the model. |
|
I will be working on a fix for this | |
After some more testing it seems to be exponential not infinite. For each one you destroy 2 new respawn. Seems to apply to all entities that can respawn at least bound to keeps. Picture of 8 Siege Merchants at Charon's Keep |
|
My guess is that it does have to do with the appearance change of todays patch (2023-08-23) that respawns the "old entity" (original model) as well as creates a new entity (new model) | |
Thanks for these notes. They were a great help into tracking down the issues. I have it fixed and it will go live in a hotfix. For reference for the latest patch we changed how resurrection happens due to a bug where the state of the timer system would be reset while it was currently operating which lead to some bugs. The new system wasn't implemented properly for Fort NPCs and Keep NPCs, which has now been fixed. Thank you again. |
|
A fix for this issue has been deployed to the live server. Thanks, Max |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2023-08-23 20:14 | Rapzel | New Issue | |
2023-08-23 20:14 | Rapzel | File Added: image.png | |
2023-08-23 20:14 | Rapzel | File Added: image-2.png | |
2023-08-23 20:23 | MaxHayman | Note Added: 0039913 | |
2023-08-23 20:34 | Rapzel | Note Added: 0039914 | |
2023-08-23 20:34 | Rapzel | File Added: image-3.png | |
2023-08-23 20:34 | Rapzel | File Added: image-4.png | |
2023-08-23 20:34 | Rapzel | File Added: image-5.png | |
2023-08-23 20:42 | MaxHayman | Assigned To | => MaxHayman |
2023-08-23 20:42 | MaxHayman | Status | new => confirmed |
2023-08-23 20:42 | MaxHayman | Note Added: 0039915 | |
2023-08-23 21:02 | Rapzel | Note Added: 0039918 | |
2023-08-23 21:02 | Rapzel | File Added: image-6.png | |
2023-08-23 21:06 | Rapzel | Note Added: 0039919 | |
2023-08-23 21:12 | MaxHayman | Status | confirmed => resolved |
2023-08-23 21:12 | MaxHayman | Resolution | open => fixed |
2023-08-23 21:12 | MaxHayman | Note Added: 0039920 | |
2023-08-24 07:20 | MaxHayman | Relationship added | related to 0021013 |
2023-08-24 07:42 | MaxHayman | Status | resolved => closed |
2023-08-24 07:42 | MaxHayman | Note Added: 0039927 |