• New Horizons on Maelstrom
    Maelstrom New Horizons


    Visit our website www.piratehorizons.com to quickly find download links for the newest versions of our New Horizons mods Beyond New Horizons and Maelstrom New Horizons!

Solved Build 14: New Installer Method for Testing and Feedback

When should we switch to using this new method?


  • Total voters
    26
So when I made a new archive, it ended up substantially bigger. But I haven't a clue why.
This couldn't just be simple, could it? I am going to be so very, very happy when Beta 4.0 is released.
I have just plain had enough of it. :sick
 
So when I made a new archive, it ended up substantially bigger. But I haven't a clue why.
This couldn't just be simple, could it? I am going to be so very, very happy when Beta 4.0 is released.
I have just plain had enough of it. :sick
So if it is just ai_ship and maximus_functions changed plus enforced new game can't you do that in the exe, keeping the old cab as that smaller compile/download of 2.7 Gb and save you the recompile problem and uploads?
 
So if it is just ai_ship and maximus_functions changed plus enforced new game can't you do that in the exe, keeping the old cab as that smaller compile/download of 2.7 Gb and save you the recompile problem and uploads?
I think that is indeed the best thing to do. Not the cleanest solution, which is why I don't like it, but probably the safest.
 
So if it is just ai_ship and maximus_functions changed plus enforced new game can't you do that in the exe, keeping the old cab as that smaller compile/download of 2.7 Gb and save you the recompile problem and uploads?
My final check on the filesize differences turned out inconclusive. So I have done what you suggested.

EXEs updated accordingly:

PiratesAhoy! Build:
http://www.piratesahoy.net/build/potc/b14_beta4_installer.exe
http://www.piratesahoy.net/build/potc/b14_beta4_final.tar

Bowengames PotC:
http://piratesahoy.bowengames.com/potc/b14_beta4_installer.exe
http://piratesahoy.bowengames.com/potc/b14_beta4_final.tar

Also, I decided I will not support ANY modpack versions older than this 2 April 2016 version because I'm afraid I cannot afford to.
Tomorrow the only thing I will do is to write the release article. I want to make no further changes for a while now.
 
Last edited:
ModDB apparently doesn't allow "CAB" files, so I changed the extension to "TAR" instead and updated the EXE accordingly.
Links updated in my above post. This is also what should appear on ModDB very soon.

I'd much appreciate if someone could try to install from this latest EXE.
You don't need to download the TAR file if you already had the latest CAB.
Just manually change the extension; the files are identical. ;)
 
I have now played a couple of hours with this new update, and it act fine.
Thanks! Did you install from the CAB or the TAR?
If you played for several hours, I think it was probably still the CAB version because I didn't make it TAR until two hours ago.

I'd just like someone to double-check that the new EXE+TAR do actually install.
They should and probably do, but I was unable to test that myself as it was a rather last-minute change forced on me by ModDB upload restrictions. :facepalm
 
Back
Top