It seems that the correct place to put the files is under:
Code: Select all
/Users/<username>/Library/Application Support/Uplink/mods
Under this location, here is what my tree looks like with the mod installed:
Code: Select all
./data
./data/gateways
./data/gateways/NeoTrinity.txt
./graphics
./graphics/gateway
./graphics/gateway/NeoTrinity.tif
./graphics/gateway/NeoTrinity_t.tif
./music
./sounds
Starting Uplink and attempting to log in then leads to "An Uplink Assertion Failure." Here is the relevant entry in the debug.log (caching Steam ID, username removed):
Code: Select all
===============================================
NEW GAME 17:38, 8/1/2013
===============================================
Version : 1.6.6
RELEASE
Mac OS X Build
Version 1.6.6 (RELEASE)
Compiled on Aug 28 2012 at 17:49:44
Loading uplink options from /Users/<username>/Library/Application Support/Uplink/options...success
Successfully loaded data archive data.dat
Successfully loaded data archive graphics.dat
Successfully loaded data archive loading.dat
Successfully loaded data archive sounds.dat
Successfully loaded data archive music.dat
Successfully loaded data archive fonts.dat
Compiled with SDL_mixer version: 1.2.12
Running with SDL_mixer version: 1.2.12
Loading profile from /Users/<username>/Library/Application Support/Uplink/A.usr...REDSHIRT : Failed to load file : /Users/<username>/Library/Application Support/Steam/SteamApps/common/Uplink/Uplink.app/Contents/MacOS/../Resources/data/gateways/NeoTrinity.txt
An Uplink Assertion Failure has occurred
=======================================
Condition : rsFilename
Location : /Users/Andrew/Documents/UplinkMac/sources/3rdparty/uplink/source/uplink/src/world/generator/worldgenerator.cpp, line 488
============== B E G I N C O R E D U M P =================
============== E N D C O R E D U M P =====================
Setting breakpad minidump AppID = 1510
Steam_SetMinidumpSteamID: Caching Steam ID: XXXXXXXXXXXXXXXXX [API loaded no]
I have tried just about every file permission combo on the NeoTrinity files (.txt and .tif) in case that was causing them not to be read, but to no avail. Nothing about the mod-created directories' properties seem different than usual, either.
This is not a new bug by any means; there are two other reports of this happening in the Mac Uplink support forum:
http://forums.introversion.co.uk/uplink ... 484#435484
http://forums.introversion.co.uk/uplink ... 445#435445
Neither thread has a resolution posted, so I thought I would bring it to attention here. Let me know if I can provide any more info. I have not tested if other types of mods work.