Hello ! I got problem with last X mass AIMNAS & Good of Games version Jagged Alliance 2 Willd fire 6,04 Eng.

After some play with files the game start works fine but I can't attach some under barel weapons like glanade launchers or atach ceramic plates for armor or some things for pants . My Question is did you turn this out from mod or mod is not full compatybille with mod ?

All HE types of ammo with an explosion size higher than 1 explode with a smoke explosion instead of a normal explosion.

A bug with Kyle - when you bring him a deed, he just stands and game hangs. I think it happens because of big maps.

Keep the bug reports coming Tais.
About MOLLE: the issue is known for a while and it stinks, no kidding... as for a solution... there might be one, but I didn`t get it to work (using attachmentpoint slots). Getting that properly to run will most likely require a complete rework of the attachment slot system currently used in AIMNAS (I`m still using the really bad and slow item1 goes into item slots xyz instead of the much more comfortable item1 attaches to attachment point xyz which item 2, 3, 4 have... which in turn also blew up the limit of attachment slots which required an exe change, which is the reason you want to run the XMAS release with an exe newer than 7669...). I think you get the point...

So yeah, MOLLE is still an issue and I hope that it will get fixed some day (because MOLLE is awesome and I really want it to work).

Still, main project currently is getting those bloody maps done (and I`m still far from finishing it).

i am playing last xmas release and notice there is no scope penalties for very close ranges. is this how aimnas cht system works? and can you explain how can i change it. this mod is far best mod ever i played by the way.

yes i think it's open.

but still can hit very close targets. i can't post any link or ss but i cheked ini editor and it says use_new_cth_calgulator = true

got a 7x scope and still %100 hit chance a near by enemy.

You can not look through 2 optics at the same time, press . [DOT] to cycle through all available sights.

There's no Headminer in Chitzena, that's a bug right? Used the GABBI cheat and checked all sectors, some were populated and some were not but definitely no Headminer in Chitzena.

Using this version: SCI_AIMNAS_XMAS2013_Release_Feb14_Update_on_r6967_d1954

EDIT:
Just opened sector on the map editor, saw the 4 of them ready but no one spawned. I did save it but it had no effect, neither have no idea how to import this into my savegame or if is it possible to summon a "civilian entity" midgame. Thanks anyways.

Also, isn't Skyrider around Drassen anymore? Not asking for the exact location I just wanted to know if he's still in the game. He was usually a couple squares away from the airport, hiding in a cabin in the swamps.

Torres84 wrote on Tue, 27 January 2015 13:17

There's no Headminer in Chitzena, that's a bug right? Used the GABBI cheat and checked all sectors, some were populated and some were not but definitely no Headminer in Chitzena.

Using this version: SCI_AIMNAS_XMAS2013_Release_Feb14_Update_on_r6967_d1954

EDIT:
Just opened sector on the map editor, saw the 4 of them ready but no one spawned. I did save it but it had no effect, neither have no idea how to import this into my savegame or if is it possible to summon a "civilian entity" midgame. Thanks anyways.

Also, isn't Skyrider around Drassen anymore? Not asking for the exact location I just wanted to know if he's still in the game. He was usually a couple squares away from the airport, hiding in a cabin in the swamps.

Looks like someone discovered what causes the missing headminer (thanks to normat for pointing it out):

"This code in scripts/initmines.lua leaves Mountain mine in the randomization pool despite being assigned to Harvey already. As a result, it is likely that one of the other headminers is set to spawn in Mountain mine as well, leaving one of the remaining mines without a headminer altogether.

Harvey.MineID = MountainID

-- Fred is the first miner the player encounters unless it's Alma
if currentMine ~= AlmaID and currentMine ~= MountainID then
Fred.MineID = currentMine
end

-- collect IDs of all producing mines except Alma mine and Fred's
local MinesLeft = {}
for i = 1, #mines do
if i ~= AlmaID and i ~= currentMine then
if mines[i].MaxRemovalRate > 0 then
table.insert(MinesLeft, i)
end
end
end

Possible fix

In order to fix this issue, do not add Mountain mine to the randomization pool. Replace

if i ~= AlmaID and i ~= currentMine then

with

if not (i == AlmaID or i == MountainID or i == currentMine) then

to prevent it from entering the pool, so that the number of mines actually matches the number of remaining headminers."

Hello everyone,

I have the following issue - when I try to start a new game, a runtime error pops out. It happens right after the intro (switching the intro off didn't help), so the only option is to quit the game.

Link to error screenshot: https: //drive.google.com/file/d/0BxDzwpFpaFp9RVVzUkFEREQ0aUU/view?usp=sharing (delete space after https: I know it's against the rules for me as a new user to post links, but it seems to be the only way to let you know what actually happened)

I use JA2 Gold Steam version + 1.13 v.7435 updated to 7609 + AIMNAS XMAS release.

Since I have absolutely no coding skill, I have no idea, what could have caused this.
Is there any way to fix this error?

You could edit your XMLs to make all ammo lock-busting. Easy peasy.