Eliminating vanilla database errors

Thalassicus

Bytes and Nibblers
Joined
Nov 9, 2005
Messages
11,057
Location
Texas
What's the easiest way to get rid of these standard vanilla error messages in database.log? I investigated the messages, but the files they reference are somewhat obscure, and after looking around half an hour I have not yet figured out the ideal way to solve these.


[14021.962] Invalid Reference on ArtDefine_Landmarks.LayoutHandler - "SPECIAL" does not exist in ArtDefine_LandmarkTypes
[14021.962] Invalid Reference on ArtDefine_Landmarks.LayoutHandler - "SPECIAL" does not exist in ArtDefine_LandmarkTypes
[14021.962] Invalid Reference on ArtDefine_Landmarks.LayoutHandler - "SPECIAL" does not exist in ArtDefine_LandmarkTypes
[14022.914] Invalid Reference on UnitGameplay2DScripts.UnitType - "UNIT_PRIVATEER" does not exist in Units
[14022.914] Invalid Reference on UnitGameplay2DScripts.UnitType - "UNIT_SPANISH_GALLEON" does not exist in Units
[14022.914] Invalid Reference on UnitGameplay2DScripts.UnitType - "UNIT_SPANISH_TREASURE CART" does not exist in Units
[14022.914] Invalid Reference on UnitGameplay2DScripts.UnitType - "UNIT_DANISH_LONGBOAT" does not exist in Units
[14022.914] Invalid Reference on UnitGameplay2DScripts.UnitType - "UNIT_SAXON_HUSCARL" does not exist in Units
[14022.914] Invalid Reference on UnitGameplay2DScripts.UnitType - "UNIT_POLYNESIAN_WAR_CANOE" does not exist in Units
[14022.914] Invalid Reference on UnitGameplay2DScripts.UnitType - "UNIT_HITTITE_WARCHARIOT" does not exist in Units
[14022.914] Invalid Reference on UnitGameplay2DScripts.UnitType - "UNIT_SUMERIAN_PHALANX" does not exist in Units
[14022.914] Failed Validation.
 
The second group (last eight lines) are a "feature" of the way the DLC scenarios have to be written - some of the scenario content is in the core DLC and is loaded every time, some of it is only in the scenario, so is only loaded when playing the scenario - so short of removing the DLC (or always playing the scenario) there is no easy way to remove those errors - unless you want to "hack up" the DLC scenarios and move the scenario specific units into the main DLC content files.

The first group (three lines) seem to be a bug in the core xml files, pretty sure the relevant xml files are in the asset .fpk files, so removing those errors would be non-trivial
 
[14021.962] Invalid Reference on ArtDefine_Landmarks.LayoutHandler - "SPECIAL" does not exist in ArtDefine_LandmarkTypes
[14021.962] Invalid Reference on ArtDefine_Landmarks.LayoutHandler - "SPECIAL" does not exist in ArtDefine_LandmarkTypes
[14021.962] Invalid Reference on ArtDefine_Landmarks.LayoutHandler - "SPECIAL" does not exist in ArtDefine_LandmarkTypes

I wonder if updating the ArtDefine_LandmarkTypes table with an

INSERT ArtDefine_LandmarkTypes (Type, Landmarktype, FriendlyName)
SELECT 'SPECIAL', 'LandmarkHandler','Special';
would fix this error. Of course, I'm sure that would probabaly be waaay to easy :)
 
Back
Top Bottom