Well, at the moment, the only way to make things catch on fire is to get caught up in an explosion. Fire propagation has not been facilitated yet, and will be the subject of further development. I'm adding issues to the development branch

Edit: The phoenix feather thing still needs a little bit of work, like for example a message indicating that the phoenix feather material has been restored, and maybe a temporary imitation increase.

Ok there is a release available. Scroll down and you will find IvanWin051a.zip.

I made a real hash job of releasing, but at least it is a start. I'd love to find a simple way of creating a changelog and making it available in the repo somewhere?

Hehe, the merge request is up. Once merged then I will update my local copy of the IVAN051-develop branch and compile a binary for testing.

A flaming adamant sword does not sparkle.

Maybe we should just leave it at 7, it's not a biggie.

truth largecat::SpecialSaveLife()
{
  if(--Lives <= 0 || game::IsInWilderness())
    return false;
...

Looks like it is indeed 7. We can increase it to nine with our code repo if we feel so inclined...?

Is the benefit of the life-saving intrinsic bestowed on the player if she is polymorphed into a large cat?

Definitely Cap! It seems like we can also package binaries with each (pre-)release (see the github article on releases). Do you think we are ready to put out a pre-release for alpha-testing?

So am I, because I have developed quite a bit of code and I would like that tested. I am thinking about how to manage the source at the moment. I think there should be a 0.51 branch called "IVAN051-develop" which is separate from master, where we can merge changes from various forks and feature branches into, without breaking the master branch, and where we can compile beta test versions of the game.
Once we have a stable tested 0.51 beta, we can merge that into master and then move onto 0.52 development, and so on.

OK so I added the branch IVAN051-develop. With this we can merge changes into this branch, including all the bugs, and have this compiled and play-tested. I am going to try to squash a couple more bugs on my local branch. Stand by for more action soon.

Can we have alerts for IVAN community holy days?

I think this is a good idea. What I will do with the fire subsystem when I have a first iteration done is to make a pull request. I am 50% convinced that I have 70% of the work done on the fire subsystem. Once the other bits are done, I suppose we then make a thread to play-test IVAN 0.51?

I think the consensus was as per the first post in the thread. I will root around on the github site and put these milestones up.