* Changes to House Warning Messages filter
* Set HousePortal destinations based on data from database with fallback to SlumLord
* Init House from World DB if not found in Shard DB
* Update House SQL Writer
* Flags attribute
* empty statement
* Fix Formatting
* Fix OrderBy -> ThenBy
* use OfType
* Replace with asingle call to Count(...)
* Replace with a single call to FirstOrDefault
* Merge cast with type check
* use String.IsNullOrEmpty
* use collections count property
* use format specifier (results in shorter loc)
* use Any() instead of Count() > 0
* revert ThenBy with comment
The cache.bin, as well as the client use these data structs in WXYZ order.
However, when you actually construct a Quaternion in ACE (Which uses a System.Numerics native type), the arguments are passed in XYZW.
I prefer XYZW order, but, to keep things in lined with the client, I've univied angles to be WXYZ order in our cache.bin exporter and in ACE.
* This moves the .sql file generation code that Ripley has been using into ACE.Database
This will help us import data from any source into ACE EF objects, and then use these SQLWriters to create a unified output.
* Weenie and LandblockInstances SQL Writers added + Enums
Some styling and comments added to the other SQL Writer classes.
Still need to do the treasure tables, as well as recipe/cook books.
Also need to confirm SQL output is well formed and accurate.
* CookBookSQLWriter and RecipeSQLWriter
Writers that still aren't implemented:
PointsOfInterest
TreasureDeath
TreasureWielded
Also, still need to test the output of these writers to make sure it's correct.
* Formatting tweaked a little bit, much closer to the final product
This creates scripts that import.
Still need to verify a couple of data mismatches.
* This moves the Int/Did property decoder to ACE.Entity.Enum.Properties
This code will likely be used to help UI content editors and database viewers.
* This fixes float output where precision was lost. Woops.
* Fat fingered a variable in the weenie SQL writer
This concludes all the testing for the SQL Writers.
They all test OK and produce the same results as the code Ripley was using to generate the .sql files.
