FF 0.43 Bug Thread

[Thunder_Gr]

Can you please tell me if there is a way to get around that MAF I have posted a save game for?
I cannot get around it any way I know of, So if it is not possible I will have to start a new game...Again.

 

[Iceciro]

Wow, I have to echo one of the many posts - is the MASSIVE NUMBER of sea spawned baddies intentional? I cannot get off my home islands...

Secondly, should Arcane Lacuna prevent Patrian Awakened from being able to join cities? That bites... a lot.

 

[ShadowOfADoubt]

Currently (Patch D) as the Svart I can build under a normal forest fine, but building under an ancient forest destroys it. I'm assuming this isn't desired behavior, because the build button doesn't say will chop forest.

 

[vivictius]

What needs to be changed to premade maps in order to use them now? Everyone one I have tried, including ones for earlier version of FF, cause a CTD. This includes ones that work in the current version of FfH.

 

[xienwolf]

Max number of players is now 50 instead of 35

 

[vivictius]

Ah, ok, I even know how to fix that, thanks (-:

 

[vivictius]

Hum... well, it kind of works, I am now, however, getting an error -

File "CvEventInterface", line 30, in onEvent
...
...
...
NameError: global name 'iAttacker' is not defined


isnt an 'iAttacker' Apples UU warrior replacement? (-:

 

[Bezhukov]

I'm getting the CTD's at the point when all Hell (literally) breaks loose. In my latest game, the AC was only on 23%, but once Hyborem came on the scene, I saw a Wraith, an Azer, and two Water Elementals spawn near him in one turn. An earlier game he spawned across the map and I started getting messages that the Demonic Hordes were conquering an AI city or two a turn. Is this intended?

 

[Vehem]

Hum... well, it kind of works, I am now, however, getting an error -

File "CvEventInterface", line 30, in onEvent
...
...
...
NameError: global name 'iAttacker' is not defined

Can you post a couple of lines above the NameError line - the last file/line number mentioned in the list is the more accurate location of the problem. The CvEventInterface line just says where the current set of calls came from initially...