[2.33] Maybe I know why Family Bliss achievement doesn't runs correctly

[Matt Zhuang]

Although it is written wrong in achievements.txt (see 4F) not in achievement_events.txt . HOWEVER , any_close_relative command doesn't work and this command may cause other decision(event, etc) after this command to run mistakenly.

# Family Bliss
character_event = {
　　id = 721
　　hide_window = yes

　　ai = no

　　trigger = {
　　　　NOT = { has_character_flag = achievement_family_bliss }
　　　　any_close_relative = {
　　　　　　count = 6
　　　　　　is_friend = ROOT
　　　　}
　　}

　　mean_time_to_happen = {
　　　　days = 1
　　}
　　
　　immediate = {
　　　　set_character_flag = achievement_family_bliss
　　}
}

Why I found this bug ? When I used this any_close_relative command ,the decisions after it crashed , but after I deleted any_close_relative = { } , the whole decisions TEXT worked rightly !

 

[Relavo]

Hope this would be fixed

 

[Dracko81]

You are wrong. The reason it doesn't work is because it has the same trigger requirements as mudslinger. If you get mudslinger, you get family bliss.

 

[Matt Zhuang]

You are wrong. The reason it doesn't work is because it has the same trigger requirements as mudslinger. If you get mudslinger, you get family bliss.

So the bug is in achievements.txt

# Mudslinger
...
MUDSLINGER = {
    possible = {
        is_ironman = yes
        NOT = { has_character_flag = achievement_mudslinger }
    }
 
    happened = {
        has_character_flag = achievement_mudslinger
    }
}

# Family Bliss
FAMILY_BLISS = {
    possible = {
        is_ironman = yes
        NOT = { has_character_flag = achievement_mudslinger }
    }
 
    happened = {
        has_character_flag = achievement_mudslinger
    }
}


# We're In Business
WERE_IN_BUSINESS = {
    possible = {
        is_ironman = yes
        NOT = { has_character_flag = achievement_were_in_business }
    }
 
    happened = {
        has_character_flag = achievement_were_in_business
    }
}
...

......You say rightly,BUT any_close_relative CANNOT WORK and causes my decisions which were after this command crashed!!
PS 1. I googled it and found somebody found this command cannot work ,too)
PS 2. He also found random_close_relative cannot work...

 

[Servancour]

I took a look at the achievement. We know of the issue that the achievement itself has the wrong character flag set in order to unlock. We are working on this already, but I did test it in order to check if it actually works. There may indeed be an issue with the event that gives you the correct flag, probably because of the trigger. So I filed a new bug report for that issue.

Thank you for reporting!

 

[grisamentum]

You are wrong. The reason it doesn't work is because it has the same trigger requirements as mudslinger. If you get mudslinger, you get family bliss.

No, you are completely wrong. Moreover your post is totally illogical, because there could (and in this case, there are) two reasons an achievement does not work. Even if the achievement correctly required the family bliss flag, the family bliss flag would never work because any_close_relative doesn't work.

 

[Dracko81]

No, you are completely wrong. Moreover your post is totally illogical, because there could (and in this case, there are) two reasons an achievement does not work. Even if the achievement correctly required the family bliss flag, the family bliss flag would never work because any_close_relative doesn't work.

Except the OP didn't mention that in the OP. Hence the edit after my post. Please do pay attention.

 

[grisamentum]

Except the OP didn't mention that in the OP. Hence the edit after my post. Please do pay attention.

On the contrary, the original version did explain that "any_close_relative" doesn't work. Which you just ignored when you claimed he was wrong.

 

[Dracko81]

Yes but it isn't the reason the achievement didn't work correctly, as per the thread title. The reason it doesn't work correctly is because of the mudslinger issue, not because of the other issue. I never said the other wasn't an issue, only that it wasn't the cause for the improperly running of the event.

 

[grisamentum]

Yes but it isn't the reason the achievement didn't work correctly, as per the thread title. The reason it doesn't work correctly is because of the mudslinger issue, not because of the other issue. I never said the other wasn't an issue, only that it wasn't the cause for the improperly running of the event.

Except that you're wrong - they are both reasons that the achievement doesn't work correctly. Even if the Mudslinger issue was fixed in achievements.txt, the Family Bliss achievement would still not work correctly. The title is correct.

It is ALSO true that the Mudslinger duplication needs to be fixed. Both problems equally stop the achievement from working, and both need to be fixed. So you are simply wrong when you said to him, "you are wrong, the reason is X." Yes, X is a reason, but the OP is also correct that he identified a separate and equally important reason the Family Bliss achievement will not work.

only that it wasn't the cause for the improperly running of the event.

And that's actually where you're completely wrong. The Family Bliss event never runs in the first place, because any_close_relative will never run.

The other problem was that even if the event could successfully run (which it can't), it gives you a flag that isn't tied to an achievement. The OP is 100% correct when he says that broken any_close_relative is why the Family Bliss event won't run.

The Mudslinger bug has absolutely no relationship to this bug. You just jumped on a bug and confused the issue by bringing up an unrelated problem.

 

[Dracko81]

He didn't say the family bliss event, he said the achievement. The event =/= the achievement. The achievement doesn't work properly because of wrong flags.

You arguing semantics as you always do. I am not wrong, my statement was correct. The OP's statement that the achievement didn't work because of the any_close_relative was wrong.

 

[grisamentum]

He didn't say the family bliss event, he said the achievement. The event =/= the achievement.

1. He did say the event. Read the OP. It even has the event code in it.
2. No, YOU said the event. You JUST said "I never said the other wasn't an issue, only that it wasn't the cause for the improperly running of the event." And again, you clearly didn't read his actual post, because he said:

HOWEVER , any_close_relative command doesn't work and this command may cause other decision(event, etc) after this command to run mistakenly.

And that he provided the code for the Family Bliss event. He so obviously referred to the event, but you didn't read the OP, just the title.

The achievement doesn't work properly because of wrong flags.

But even if the flags are correct, the achievement would still not work because the event is broken. As the OP explained, and you ignored.

You arguing semantics as you always do. I am not wrong, my statement was correct. The OP's statement that the achievement didn't work because of the any_close_relative was wrong.

It's not wrong! Even if achievements.txt is patched tomorrow to call for the correct flags, the achievement still won't work unless the any_close_relative scope is fixed. The achievement will still be broken.

 

[Korbah]

Arguing over content of posts doesn't help with the resolution of ingame issues. QA have already responded and are aware of the issues. If you both feel the need to continue discussing this, take it to private messages.