Michael Cook (mackal) 501204a4d2 Add hot_zone filtering for global loot
We do this in GlobalLootEntry::PassesRules since we want to check if the
hot zone status changes during run time

Value can be null, if null it's not checked. If the value is 0 the zone
must not be a hot zone (I guess one might want that) and if it's not 0,
the zone must be a hot zone
2020-02-06 01:52:35 -05:00
..
2014-03-22 05:17:38 -04:00

On the move from svn -> git we lost the ability to track revision numbers on the repo.

No big deal!

What we'll do instead as follows:

-Optional SQL updates go in optional/
-Required SQL updates go in required/
All updates will follow a specific format of YYYY_MM_DD_Desc.sql, this is so it's easy to sort.

So the following is a good example of what I expect to see
2013_02_16_GitConversion.sql


The new bots/ folder contains two sub-folders named optional/ and required/ for updates.