For an unknown reason, the game thinks that l_attr.set_corruption is an integer with a value of 1 at this point. An integer and a function can not share the same name.
I don't know where that value was assigned, I suspect that it was one of the previous versions of the game, since I'm using an old save.
___________________
Alright, I was right! In v0.6 day12.rpy line 591:
Code:
$ l_attr.set_corruption = +1
It creates an integer with the name of the function and a value of 1
You obviously just forgot the brackets and this little typo creates a mess :biggrin:
Can't call the function after that any more, because it's a variable now.
_________________________
@Fission Mailed
For those with the same error that is caused by the save from the bug of the previous version, this is how to fix it without going back to pre-0.6 saves:
Open console (Ctrl+O) and first check that this is the same problem - take a look at the value of the variable - type:
l_attr.set_corruption
If the answer is "1" (or some other integer), then delete the variable - type:
$ del l_attr.set_corruption
Now hit the cursor up key (up arrow) twice to get to the l_attr.set_corruption again and check the value. It shouldn't be an integer any more. It should give you "<bound method .... "
Now the function should work fine again.
But since you missed that one corruption point because of the bugged line in version 0.6, you should add one corruption point to Liza. First check the value of Liza corruption - type:
l_attr.get_corruption()
Now increase corruption - type:
$ l_attr.set_corruption(+1)
Check the value again (up arrow twice):
l_attr.get_corruption()
Exit console (Escape-key). Save the game at this point to a memory slot that you will remember. This is a fixed save now, the previous ones from v0.6 and v0.7 after that are buggy.