Object transfer lag bug #4554
Comments
Per changed blocking which not transferred by tractive |
Per changed blockedby which not transferred by tractive |
Per commented Interesting. I wonder what the correct solution is - to reduce the body points to the research level of the receiving player, or to remove the sanity check against this, allowing you to have superior units received by other players... |
Berserk Cyborg commented Keeping the superior droid would be more 'realistic' since they have the new research applied to them anyway... Though if there is a way that object transfers can be used to cheat somehow, then just reduce to the research levels of the receiving player just to be safe. |
Cyp <cyp@...> changed status from |
Cyp <cyp@...> changed owner from `` to |
Cyp <cyp@...> changed resolution from `` to |
Cyp <cyp@...> commented In Warzone2100/warzone2100@d0934ff:
|
resolution_fixed
type_bug
| by Berserk CyborgI have been encountering an issue that I was finally able to reproduce at a consistent rate now. What happens is that if a droid is transferred with either a Nexus Link or donateObject(), then the log file will assert with something that looks like this:
This will then produce more and more lag (with a rapidly growing log file) with each successive bad transfer.
I discovered is that if the droid is taken from an enemy player with superior research (defense upgrades?), then this issue happens.
Issue migrated from trac:4554 at 2022-04-16 12:40:14 -0700
The text was updated successfully, but these errors were encountered: