-
Notifications
You must be signed in to change notification settings - Fork 155
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inara plugin: Incorrect format of opponentName parameter or it is completely missing. #1732
Comments
Technically I think we're in compliance with the Inara API documentation for this. So, over to @clonedArtie to comment as to if he wants to update the documentation to "only send non-empty strings", and just not send the event at all if we can't get a value for |
Artie has informed me that for required properties in Inara API messages So I'll adjust EDMC code, for the 5.6.1 bugfix release coming soon, to add a check for that. |
@chennin I've not played to know. Was that caused by an "in supercruise, not jumping" Thargoid interdiction? If so, was it an inevitable interdiction, or do you know for sure these can be escaped (i.e. win the mini-game) ? Specifically I'm wondering if there can be an |
It's supercruise, yes. The interdiction is very hard and I have not seen anyone win it yet, but I do not know if it is impossible. |
OK, thanks for the info. I've implemented a paranoia check for that anyway. |
Please check the Known Issues in case this has already been reported.
Please also check if the issue is covered in our Troubleshooting Guide. It might be something with a known work around, or where a third party (such as EDSM) is causing logging that is harmless.
Please complete the following information:
EDMarketConnector.log
EDMarketConnector-debug.log
Describe the bug
Interdiction by a Thargoid throws a WARNING
Corresponding journal entry:
Journal.2022-11-30T111811.01.log
Ultimately sounds like a game journal bug to me, but you might want to handle that and silence the warning?
The text was updated successfully, but these errors were encountered: