Stock Game = You destroy the fort's cannons, then fight the soldiers in the fort and you get:
> Money + free ship repair

Capture Colonies = You destroy the fort's cannons, then fight the soldiers in the fort AND town and you get a choice:
1. Take the money
2. Give the town to another nation for increased rank with that nation
3. Take the town for yourself and assign your own governor and fort commander

So in the stock game, you could only loot towns, but not actually capture them. Now you can.

Talisman, I got that crazy crewmember thing as well when boarding a Lugger3 with the RN_Corvette:
That was "BOARDING_ShipDeck4" aka "locations\decks\deckLow".

Could that be due to my code change that makes use of ONE MORE locator number before cycling back through existing ones?
That WAS necessary for the forts and towns, otherwise not all locators would be used.

Perhaps all boarding decks need double-checking; they might all have one locator less than they should have.
Alternatively, I could change the code so that "reusing" will happen differently depending on it being a fort/town or a ship.

1. installed the original game
2. put the installer beta 3 full and the Sept 18 update in the same folder
3. let the installer do its thing
4. Started the game and got the runtime error which as you said, suggests the update is not making into the game folder, but since beta 3 clearly did I am at a loss to understand what is going on. it seems to me that either the sequence is used is incorrect, the installer is not working properly or the there is an error in the update file.

I thought the installer couldn't read the two other files if they're not a 7zip file? And so I downloaded 7z before even trying the new way to install back then.

Click to expand...

The installer takes care of the unzipping on its own; you shouldn't need 7-Zip on your computer at all.
However, for some strange reason, Jason's computer is apparently not letting the updated files make it all the way into his game folder.
NOT normal.

1. installed the original game
2. put the installer beta 3 full and the Sept 18 update in the same folder
3. let the installer do its thing
4. Started the game and got the runtime error which as you said, suggests the update is not making into the game folder, but since beta 3 clearly did I am at a loss to understand what is going on. it seems to me that either the sequence is used is incorrect, the installer is not working properly or the there is an error in the update file.

Click to expand...

With step 2, are you putting the installer files in their own separate folder, or into the game folder itself?
If they're placed in the game folder, they might not work as intended, so a separate folder might be best.

When I went to download the latest update 89.6 gig it sent to an update of 77 gig which I think is the old one.

Click to expand...

77 GIGS? Should be MBs on the update at the very least.
So you're saying your downloaded files are .RAR ones? That.... doesn't make much sense. They're definitely 7-Zip.

To me, it sounds as if the new EXE file is installing an OLD update file. That would cause a problem.
Either that, or Windows Security Stupidity is killing things. Again. Like it usually does.

I see a couple of options here:
1. Check if at least some of the code files are making it in by viewing PROGRAM\globals.c as I suggested in the other thread
2. Extract the Update 7-Zip archive manually, then move the files contained in it into your game folder
3. Wait until next weekend when I post the FULL public release; after all, the full archive DID install properly for you, right?
The problem only started occurring when I renamed the BOAL_deck.c file to LAi_deck.c and moved it to another folder.

Just for the sake of it, can you open your PROGRAM\globals.c file and check what it says all the way at the bottom?
There should be these two lines:

Code:

#define BUILDVERSION "14 Beta 3 Test: 21 Sep 2013" // this is not used in reinit.c anymore, so we can use a string now
#define IS_SGV 14.887 // must be a float - use small numbers to keep them sequential for all these updates --> 12.10 is smaller than 12.9!

With step 2, are you putting the installer files in their own separate folder, or into the game folder itself?
If they're placed in the game folder, they might not work as intended, so a separate folder might be best.

Click to expand...

The installer will give an error message if you try that and refuse to continue. So that shouldn't be going wrong.

Talisman, any chance you could update a bunch of those town capture boarding locators before the coming weekend?
That's when I intend to release Beta 3 and it would be quite nice to at least have those "floating crewmembers" fixed.

Talisman, I got that crazy crewmember thing as well when boarding a Lugger3 with the RN_Corvette:View attachment 12576
That was "BOARDING_ShipDeck4" aka "locations\decks\deckLow".

Could that be due to my code change that makes use of ONE MORE locator number before cycling back through existing ones?
That WAS necessary for the forts and towns, otherwise not all locators would be used.

Perhaps all boarding decks need double-checking; they might all have one locator less than they should have.
Alternatively, I could change the code so that "reusing" will happen differently depending on it being a fort/town or a ship.

Click to expand...

Could be - but I am not sure I actually understand what you are saying.

Talisman, any chance you could update a bunch of those town capture boarding locators before the coming weekend?
That's when I intend to release Beta 3 and it would be quite nice to at least have those "floating crewmembers" fixed.

Click to expand...

Not sure --though I hope to have some done by mid-week ( wednesday ) - getting myself up to a level to attack forts without using the console ( so I get Officers to come with me ) is taking a bit longer than I expected.

Do you know the Locator file for Cartegena Port - I would like to get the guy out of the water at least.