Queries database then scans corresponding SQL file, replacing values
in INSERT statements with data from the database.
Is not smart about which INSERT statement gets which data; line-end
comments can get shuffled around if SQL file INSERTs are out of order
or missing. If you're doing INSERT or DELETE operations, make sure
to add a blank "INSERT INTO `table` VALUES ();" or manually remove
the INSERT statement respectively before dumping tables.
- Add res-ranks and remove elemental SDT to mobs up to entry 514.
- Separates duplicate resistant ids and more accurately defines what they are used for
Per info on JP wiki, Darkstar was chasing a magic hit rate model that no longer exists.
Todo: wipe those sdt values in the table, after ranks are set up.
* CoP - Dawn Adjustments
* Small Fixes + Battlefield loss kickout
* Add accidentally deleted mod back
* Add accidentally deleted mod back
* Fix Styling + Minor # Issues
MyISAM = table level locking, fast but not safe for multiple simultaneous writes
InnoDB = row level locking, slow, but is safe for multiple simultaneous writes
```
Features MyISAM InnoDB
Type Non-Transactional Transactional
Locking Table locking Row-level locking
Foreign keys No Yes
Table, index, data storage Three separate files Combined Tablespace
ACID No Yes
```
I have separated SDT from Resistance. Even if retail pairs these effects (I believe wiki terminology is confused and this is not the case),
we need separate modifiers to accurately represent the changes - one value will not fit both effects under our core, and we -want- to be able to adjust them separately anyway rather than code for edge case exceptions.
Item mods may need correction - a lot of past contributions in old DSP used the mods interchangeable, and at several points in project history these were flipped to be the opposite of what they were. This means that for everything I fixed, I am positive I also broke things. Followup commits to handle that aspect coming soon.
