Closed Darkcyde13 closed 2 years ago
They are not triggering because we currently create a new carrier object from the Frontier API. We can add some code to do so from the CarrierStats
event too which should correct this (I had planned to do this but apparently forgot - easy enough to add to the next release).
What's Wrong (please be as specific as possible)
Expected
The carrier event scripts to run when I change something in the carrier management screen.
Observed
Some events do not trigger and the scripts do not run.
Steps to reproduce
Configuration
My Investigation
Investigation Notes
I've been trying to get the 'carrier.name' to populate, and was wondering what events would cause it to be. I first tried changing the docking permissions, and realised that the event was not triggering to report the changes.
So I tried the following:
None of them triggered the respective events. I did add "done." to those scripts with no default before I tried, just to make sure.
I noted that the Journal events were written as soon as I made the changes in the interface, so I would have assumed the events should have triggered at that moment too.
I also checked to make sure the events were enabled this time! ;)
I've not tried everything, as I don't want to initiate a decommission or a jump at the moment (although I know I can cancel them).
EDDI Logs
N/A
Player journals
Journal Entries: