ILLiad Known Issues
5 results found
-
Byte arrays passed to .NET methods are converted to null due to an NLua bug
Byte arrays (often referred to as Byte[] in Microsoft's .NET documentation) passed from Lua to .NET methods are converted to null, causing those .NET methods to fail when included in addon code.
This is a known NLua bug present in the version of the NLua component used by the ILLiad application, detailed here: https://github.com/NLua/NLua/issues/438.
Bug# 24017
0 votes -
Some server addons may not log errors
Certain kinds of server addons may experience an issue where errors are not logged. INFO and DEBUG entries for the addon will still log properly.
Bug #16386
0 votes -
Google Search v2.1 Addon Broken
There is an issue causing version 2.1.0 of the Google Search addon to pull up a blank, white screen, and disable the addon's buttons.
[NOTE]: This issue is resolved in ILLiad 9.2.
Bug# 13090
0 votes -
Alma NCIP Addon sometimes performs improper error handling
In some cases, an error response from the NCIP server is not handled properly by the addon. The NCIP message validation and error handling should be improved to handle these cases.
Bug# 12033
0 votes -
System addons that explicitly set FormNames can result in loading the addon multiple times
If a system addon is created but FormNames are also entered, the addon will be loaded for both the system script environment and for each form script environment that is specified. An example where this causes errors is when registering system event handlers which can only be registered to a single addon.
Forms are not relevent in Library, System, or Server addons.0 votes