Mystery Of Tyskie Islands - Fixed file - Doom II

Firstly, this is not my work, I only contributed some fixes (detailed below). The mod was created by WojtTheDoomer - WojtTheDoomer has a YouTube channel here: Wojti 2000 YouTube.

Next, see the ZDoom thread for details of the Mystery Of Tyskie Islands release:
MOTI ZDoom Forums.

Taken from the description on the ZDoom thread:

Plot:
It's 1912. You are Frank Masseur, an Austro-Hungarian soldier that one day on trip to Guinea washes ashore a mysterious, Oceanic island. Soon enough you realise that this island used to be peaceful and filled with people...until a dictator named Pica haven't managed to get his position and turn it into a police state in which everyone has to be perfectly like Pica wants them to be, or else they will be send into a murderous machine known as CREC-001, or tortured. It is up to you to travel through the archipelago and talk to Pica...in lead-ish preferably.

Features:
-Large, realsitic jungle areas.
-3D models!
-Authentic 1910's and 1890's weaponry.
-Fighting with enemies everywhere! In the jungle, outside the jungle, OVER the jungle!
-Stylized architecture, featuring Indonesian-esque houses, steam-filled guts of machines and more!

The fixes that I've made are as follows:

-The revolver, rifle and shotgun now only use one ammo per shot as intended.
-The sprite bugs with the food barrels and a palm tree have been fixed by renaming them so that they don't conflict with Doom's own actors.
-Some duplicate actors renamed to prevent the warning messages in GZDoom.
-I've reworked the LOCKDEFS file so that the new keys used in the mod work correctly (showing the correct description whilst still working with the appropriate doors).

UPDATE: At some point, WojtTheDoomer released a v2 download link on the ZDoom page which has the fixes I provided, so I believe that this file and the one linked to on the ZDoom forum page are now identical.

Update 11/08/2018: Just noticed that the mod doesn't launch on the latest GZDoom development versions (I've not checked the 3.5.0 stable release, though). It was caused by a badly formed cluster definition in the MAPINFO file, so was easily corrected.