Fieldwork Whitelist for New Types
Investigating
This is just one example, I have not checked the rest of the DLC/Update however this new Type LCDPanelsBlock is not exposed to the whitelist and so it must either be excluded from App scripts (TSS) or it will cause a crash, any other new block types introduced in this or other updates or DLC which are not included in whitelisting will cause a similar issue. This is not something that I am aware of a work around for as this prevents toolbar and UI registration.
I have the same bug
To clarify: this primarily impacts scripting cases where controls or toolbar actions are registered using AddControl<T>() or similar API calls. These require a public IMy* type as the generic parameter, and currently, LCDPanelsBlock doesn't appear to be exposed through the whitelist in that way.
Without an accessible type, it's not possible to bind UI elements or actions to blocks using this class, which limits support in TSS apps and similar systems. If additional blocks are introduced using unexposed types, they may run into similar limitations.
To clarify: this primarily impacts scripting cases where controls or toolbar actions are registered using AddControl<T>() or similar API calls. These require a public IMy* type as the generic parameter, and currently, LCDPanelsBlock doesn't appear to be exposed through the whitelist in that way.
Without an accessible type, it's not possible to bind UI elements or actions to blocks using this class, which limits support in TSS apps and similar systems. If additional blocks are introduced using unexposed types, they may run into similar limitations.
Hello Engineer,
We've released a new update for Space Engineers.
When you have a moment, could you please update your game to version 208 and verify whether the issue you reported is still occurring?
Your feedback will help us ensure the problem is fully resolved.
Kind regards,
Keen Software House:
QA Department
Hello Engineer,
We've released a new update for Space Engineers.
When you have a moment, could you please update your game to version 208 and verify whether the issue you reported is still occurring?
Your feedback will help us ensure the problem is fully resolved.
Kind regards,
Keen Software House:
QA Department
Replies have been locked on this page!