Closed ApacheTech closed 2 years ago
Developer Notes:
So far as I can see, this can be attributed to the same bug in ApiEx.Side
, where ThreadPool threads are cached, and then recycled. This should be an edge-case bug, because this method has been used for years with no issues. If problems persist, I'll need to revert to the original design for the RelativeToSpawn()
method, where the API is passed as a parameter.
So far, this method has only ever been used on the Client, so it would be safe to ensure it's only used there by using ApiEx.Client
directly; but this seems like kicking the can down the road. The crux of the issue lies in the ability to correctly identify the app-side, without having direct access to a CoreAPI that has been passed to us from the game, within the same scope.
(Hopefully) Fixed in 2.1.0.
Describe the Bug:
To Reproduce: Steps to reproduce the behaviour:
Expected Behaviour: The game shouldn't crash to desktop, and two waypoints should be added to the map.
Additional Context