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.
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
```
- Rebranding.
- Migrate to GitLab.
- Add support for database updates when using Docker.
- Give purpose to version.h (adjust minor version with client updates).
- Add an in-game `!ver` command.
- Remove references to AGPL.
- Implement TextIDs for the monsters. Thanks @gedads for some initial
values
- Tighten battle transition timings after more retail video research
- Guard mob vars during stage transition with IsAlive(). Should
eliminate the need for the core hack
- Move player spawn position up slightly to avoid camera glitches
on entering.
This mission is a 3-stage Instance Battle at Nyzul Isle
The initial entry key item is obtained at the end of the previous
mission from Rodin-Comidin. If you lose the battle, you will have
to go back to him and obtain another.
Prior to the battle, the player must get a cutscene at the blank
next to the Nyzul Isle staging point. After receiving the cutscene,
the player can no longer enter Salaheem's Sentinels until the
mission is complete.
Naja will assist the player during this battle. If she dies, then
the player loses the battle automatically. Naja will attack a
random enemy during the fight.
NOTE: This commit contains an ugly hack for entry into Nyzul Isle.
For some reason that I have not been able to figure out, the entry
event will spam onEventUpdate uncontrollable. A double-lock is used
to trap and ignore the spam while the instance loads. This works
fine, but should be removed as soon as someone can figure out why
the spam is happening in the first place.
Sources:
http://ffxiclopedia.wikia.com/wiki/Path_of_Darknesshttps://www.bg-wiki.com/bg/Aht_Urhgan_Mission_42
gedads data: http://pastebin.com/w0TqRPMy
Instanced fight in Periqia. Requires a special assault permit
key item. The player receives one to start with from the previous
missions. Replacements can be obtained once per Vana'diel day
at the staging point if the player loses the instance. Party
members do not need a key item to assist.
The fight is against 10 lamia. BGWiki says a random amount must
be defeated. FFXIcyclopedia says 3, but that may have been that
person's experience. In this implementation, a random amount
of at least 3 is required to complete the instance.
The following things need to be confirmed to improve this fight
-Instance ID:
This is most assuredly wrong, but it wasn't on the list. Picked
one out of the way. The menu comes up right and it works, but
a message is printed to the player saying they are doing
Better Than One when they zone in. This does not effect the
mission. Playing with the CS params & instance id did not make
a difference on this. I'm not sure why this is.
-Starting position. Made up a position based off of watching some
youtube clips. Works for now, and easily fixed in the SQL when we
have a real one
Sources:
http://ffxiclopedia.wikia.com/wiki/Shades_of_Vengeancehttps://www.bg-wiki.com/bg/Aht_Urhgan_Mission_31
gedads data: http://pastebin.com/w0TqRPMy
Instanced battle on the Ashu Talif. There are two waves
in this fight. An initial wave of 5, then a wave of 4
plus the captain.
The captain is initially untargetable and up on high.
After the crew is engaged, he will jump down with a
special animation and join the battle.
When the captain has <=20% HP left, he will give up.
Everyone will disengage and the instance will end in
a cutscene.
Gessho will assist the player in battle. If the players
stalls for too long, he will attack on his own, otherwise
he will assist the players when they engage. Gessho is
allowed to die in this battle and it does not constitute
a failure of the mission.
Sources:
http://ffxiclopedia.wikia.com/wiki/The_Black_Coffinhttps://www.bg-wiki.com/bg/Aht_Urhgan_Mission_15
gedads data: http://pastebin.com/w0TqRPMy
