Compilation of Bugs from the 'Bug' Thread, after patch k

[PacoDeth]

ah well, I stand by my statement that a bug is indeed a bug and should be addressed accordingly (although obviously not in this thread as you have made it clear this is single player only), I just hope it gets addressed someday. And starting threads related to OOS have been an often ignored failure up to this point.

The only reason I pointed out the single player thing is because I wanted to point out that I never would have mentioned OOS if I had known this was a single player only thread. It was never discussed in "this thread" that it was such, and if you want to lambast people for not reading the entire "bug thread" and finding out the source of everything, instead of coming here to read the compilation of that thread (which you created for that purpose) then that is your right.

Anyways, I'm done here, sorry I hijacked this thread, I hope you continue to bring it back to it's purpose and supplying the community with a comprehensive list of single player FFH bugs. I'm gonna go hibernate again until someone mentions OOS again in any sort of positive light, until then I'll keep dreaming of the day I can play FFH with my friends again.

 

[Breunor]

ah well, I stand by my statement that a bug is indeed a bug and should be addressed accordingly (although obviously not in this thread as you have made it clear this is single player only), I just hope it gets addressed someday. And starting threads related to OOS have been an often ignored failure up to this point.

I suspect that the OOS threads haven't been that successful because they seem to start with somebody giving his/her experience and then hoping the thread will fill out. A multi-player bug thread may have more success if it goes back over the original bug thread, and records all of the instances and examples that have occurred; I learned this technique from Xienwolf and I think it works.

The only reason I pointed out the single player thing is because I wanted to point out that I never would have mentioned OOS if I had known this was a single player only thread. It was never discussed in "this thread" that it was such, and if you want to lambast people for not reading the entire "bug thread" and finding out the source of everything, instead of coming here to read the compilation of that thread (which you created for that purpose) then that is your right.

I'm not lambasting anyone for not reading the whole thread. I am lambasting you because I told you after your original post that it was a single person thread and why I did it that way. I don't understand why that wasn't good enough?

Why does it matter whether I had said previously it was a single-person thread before or not? You asked about OOS errors, I told you it was a single person thread and that I thought many if not most of the OOS errors came form bugs affecting single person play. That should have been enough for you to keep multi-player issues out.

But you couldn't just accept what I did for what it was. You decided to come back and discuss multi-player bugs. I took your comments as criticism - I can't read your mind, I don't know what you intended, but I thought the comments you made were criticism of me for not pursuing multi-player bugs. So, yes, I got angry.

Anyways, I'm done here, sorry I hijacked this thread, I hope you continue to bring it back to it's purpose and supplying the community with a comprehensive list of single player FFH bugs. I'm gonna go hibernate again until someone mentions OOS again in any sort of positive light, until then I'll keep dreaming of the day I can play FFH with my friends again.

Yes, let's put this to bed and move on.

Best wishes,

Breunor

 

[Breunor]

Updated up until patch n (post 3649).

I'm trying to decide if I should start a new thread with n or continue this one. Patches n and o seem to fix most of the CtD's and WoC's. However, a lot of the lesser items remain. So I don't know if I should continue this thread and delete the fixed items, or start a new one.

For now, I've taken a middle path, identifying the items fixed in n and o in bold. Let me know that you think would be most useful, see if we can get a majority (unless I get explicit direction from Kael of course.)

Best wishes,

Breunor

 

[DaveGold]

Since it was listed as unconfirmed, I'll confirm that AI casters captured with the command promotion always have an unused promotion.

 

[Gavinfoxx]

You've gotta add a bunch of bugs in The Cult scenario... from being able to use amphibious units to get across the water when you arent supposed to, to lots and lots of weirdness with the scripted events not happening at all, to the descriptive text not happening, to the gargoyles not spawning, etc. etc.

 

[Breunor]

You've gotta add a bunch of bugs in The Cult scenario... from being able to use amphibious units to get across the water when you arent supposed to, to lots and lots of weirdness with the scripted events not happening at all, to the descriptive text not happening, to the gargoyles not spawning, etc. etc.

I originally wanted the thread for single player, general game only - the bugs in the scnearios are 'specific' to them. That is, I want there to be a separate thread for scenario bugs, since fixing a 'broken event string' is a lot different from the bugs here. This is EXACTLY why Kael originally wanted the bug thread for the general game and not for scenarios, and I'm following his logic.

I wouldn't mind compiling this kind of list but I'm not sure where to start. It would be very hard because you have to work through probably about 30 different threads and cross reference. I'm not sure if I'm up to it ....


Similarly, I'm not compiling modmod bugs here.

Best wishes,

Breunor

 

[DaveGold]

3586 – Player asked to adopt Empyrean by the AI even though there are no Empyrean cities

I'll clarify this as I've seen it happen again. After opening the Mercurian gate and taking the option to play Basium, AI opponents can ask you to change religion to one present in your old nation, even if it is not present in any Mercurian city.

 

[Tholal]

I'll clarify this as I've seen it happen again. After opening the Mercurian gate and taking the option to play Basium, AI opponents can ask you to change religion to one present in your old nation, even if it is not present in any Mercurian city.

I'd bet this bug occurs because the Mercurians are teamed with their summoner, even though they do their own diplomacy. Probably a simple fix once the right code is located.

 

[PekkaR]

I play co-op quite often and AI may indeed ask you to switch to a religion that only your teammate has. Basium is automatically in the same team with the civilization that summons him. Never really thought it as a bug (unintended feature maybe) but of course I can at least ask a human teammate to spread the religion to me.