mirror of
https://github.com/EQEmu/Server.git
synced 2025-12-11 21:01:29 +00:00
e65b61a95f
Some live tasks make new elements available without requiring all currently active ones to be completed first. This adds the `req_activity_id` field to task activities which will mark an element active if its required activity id is completed. If a valid value is set then it's used instead of checking the current step. The `step` field may still be set on rows with a valid `req_activity_id` to specify its logical step and prevent later steps from becoming active until completed. It's only ignored when deciding if the current element is active. The legacy task logic for unlocking activities was completely refactored for this. A common method has been added so both zone and world can make use of it to determine which elements are currently active. The previous step system should remain unchanged. The world logic for locking shared tasks when an element became active did not account for "sequential" mode (all steps 0), unordered steps, or gaps in step numbers. This also resolves that issue.
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.