A new IVAN release is available here: https://github.com/Attnam/ivan/releases/tag/v058

Thanks, I'm glad it worked. It's a rare thing, Sophos be praised.

I wonder whether multiple configurations can be supported in visual studio?

In your local copy of CMakeSettings.json, try changing this line: https://github.com/Attnam/ivan/blob/913b9650edd0c9de4082c6ad...

To:

 "generator": "Visual Studio 16 2019",

God this cracked me up

Time for my annual *idea*:
I wonder if we could make scars have a 50% chance of decreasing a stat, and a 50% chance of increasing a stat?

As an extension, there could be some underwater modifier that changes this ratio to 25/75, depending on how fortunate a character is when born/spawned (sporn?)
i.e.:
VERY_FORTUNATE => 25% chance a scar will decrease stat, 75% chance a scar will increase stat
FORTUNATE => 40% chance a scar will decrease stat, 60% chance a scar will increase stat
UNFORTUNATE => 60% chance a scar will decrease stat, 40% chance a scar will increase stat
VERY_UNFORTUNATE => 75% chance a scar will decrease stat, 25% chance a scar will increase stat

Static bonus seems like the best option. Either that or add the square root of the subsequent victory score.


But what would be the victory condition after the high priest victory? Do we register the score at that point and stop counting, or keep adding to the score?
After all the quests have been achieved, I guess the only thing left would be for the character to die. That would definitely be in keeping with the game

No I don't think they stack unfortunately. They should though. I think that would be cool.

I think the second-to-last build config is the one that will get you a windows build. It's currently configured to release on tags, so you'll need to do something to circumvent that.

Agreed. It has been a while. Would be good to set up another session, maybe hearing from some more recent contributors, AquariusPower and red-kangaroo spring to mind. Also good to have long time players and fans on the show, to discuss player experience and tactics.

Great work red-kangaroo. Before I can make a windows build, can you

1. Go through all the .sh files and change their permissions back to 755.
For example, in the diff on GitHub we have:

.devsPrefs/prepareUser.sh 100755 → 100644    

Means the file permissions for this shell file have changed from 755 to 644.
Follow this link to see exactly how to do it: http://linuxcommand.org/lc3_lts0090.php

After that just commit to your branch and push. I can't remember if there are any special git steps for changing file permissions.

2. Compile the code with wizard mode deactivated. Do this by omitting the

-DWIZARD

flag in

CXXFLAGS

. Then fix the compile errors you see there.

After these two steps you will see Travis light up green for all the build configs. In the first case, the release configs rely on being able to execute certain shell scripts for packaging purposes. When the file permissions change to read only, then the containers cannot execute the commands written in the scripts because that user (Travis?) no longer has permission to do anything other than read the file.
In the second case this is just a regular compile error

I ran into these problems once before, ages ago when I first started messing with this CI business. I found the chmod thing to be quite handy Linux knowledge.

Also, you should be able to build your own windows build on your personal fork by creating, for example, a release branch, and building "manually" on Travis (i.e. log on and press the button)
or even changing the yaml file to tickle up your own containers on Travis. That's how I drafted the build system without working on the live repository
Any build artifacts will just appear in the red-kangaroo/ivan releases page.