As it is I'm going to have to do that now anyway, I think. Your HAM beta looks really tasty! Too bad I can't have a 100AP HAM sandwich.

Better to rumble like rocks than tinkle like jade.
--Tao te Ching

it's my very poor translation of a Taoist proverb about the strength of common things. Serves me right for trying to be all philosophical.

Jackinthebox

I get a CTD immedialty after I see the Sirtech logo.

Marlboro Man

Not sure I understand why, it works just fine with the latest SVN. You do have to start the game with the .exe that comes with this though.

ChrisL

Hmm. I'm not sure. The build is based off the latest code in the main branch. Rev 2369 as of yesterday. So long as you have the latest version of 1.13 (the version that includes the MultiPlayer project) then you shouldn't have an issue. If you don't have the MultiPlayer update, then you might run into problems since you'll be missing an INI file (Ja2_mp.ini) the I beleive the code requires to run. Not that 100AP needs it, but since 100AP was built onto the latest code and the latest code needs it.

As far as compatability, because 100AP is written on the latest source code (which includes MP), it is not compatible with save games created with a "pre-MP" build. The MP code was introduced with rev 2124, so if you've been playing with a build prior to that, your savegame won't be compatible. But any savegame created with an MP version of the program should be fully compatible with 100AP.

Starwalker

He might also miss the TITLETEXT_MP.STI in the Data/Loadscreens-folder.
Missing this seems to be a standard error during transition from single-player-only exe to single/multi-player exe.

Getting used to the higher numbers is going to take a few sessions. "Oh look, I've got plenty of APs to be able to crouch after firing. DOH!!"

The 100AP-System is the new standard, you /can/ switch back to the 25AP-System, but this still needs a 100AP-exe to interpret the adjusted values in several XML-files properly.

well I have a question about the maximum ap's.
I tried setting the player_ap_bonus value to 40 while using the 100AP svn version and I had mercs that stopped walking in real time mode and when in turn based mode they blew all their ap's in one gunshot, they even went into negative ap values

@scheinworld: You can switch between the 25 and the 100 AP system. There is a new INI file named "APBPConstants.ini" in your Data-1.13 folder. Just change the first line AP_MAXIMUM = 100 to AP_MAXIMUM = 25 and leave the other values the same. Then you have the 25 AP system back.

[APConstants]
;***********************************************************************
;* The maximum number of Action Points a merc may have.                *
;* Should be 5x MAX_AP_CARRIED for game-balance purposes.              *
;***********************************************************************
AP_MAXIMUM = 100

etc.

You can also use the new INI Editor for changing the 100 AP System.

\Data-1.13 APBPConstants.ini:

[APConstants]
;***********************************************************************
;* The maximum number of Action Points a merc may have.                *
;* Should be 5x MAX_AP_CARRIED for game-balance purposes.              *
;***********************************************************************
AP_MAXIMUM = 100

etc.

Ahh, I only have to change the first entry and I can disregard the other entries if I want to play the game with the known classic 25 AP-system.

Actually, that isn't completely accurate. The code has hard coded "default" values. It compares these values to those read from the APBPConstants.ini file (except for AP_MAXIMUM). If they are the same, then the code automatically adjusts them for the AP_MAXIMUM value you've set. So, if you set AP_MAXIMUM = 25 and have AP_MINIMUM = 40 (and not commented out), then the code will see that it's the same as the built in default, and automatically adjust it to 10. It's only if you put in a value other then the default that the code will not make the dynamic change. I.E., if you set AP_MAXIMUM = 25 and AP_MINIMUM = 39, AP_MINIMUM will remain 39 in the code (of course, this will screw things up, but that's another issue altogether )

Starwalker, the APBPConstants.ini had to use uncommented values for it to work correctly in the new INI editor.

Ahhh, I was under the assumption that the uncommented values would always be taken, being equal to the defaults or not...