It will piss off that specific god and it will slightly piss off that god's two nearest friends (of the nearest alignments). And I guess it will therefore also slightly adjust your alignment.

There are also other places with the old mailing list / website address which should be updated, f.ex. the README. A search for "sourceforge" in the repo reveals them all, if somebody wants to fix them.

It's set up. The email is ivan-support@googlegroups.com.

Should we make the group public so that people can post there directly (and optionally view other's posts as well?) or make it private so everything must be sent via the @attnam.com address?

I'm logged in on IRC 24/7 but I haven't seen J_Kahvi there lately (if you mean #attnam). A quick check in the log says the last time he was online was in 2013.

Nice!


I can do that.

But yeah with Google Groups everybody could check them when they have some free time, so I think that's its greatest benefit.

I found out about Google Groups Collaborative Inbox (short intro video here) which seems to be just what we need to replace the old Sourceforge mailing list.

With it, people don't have to register anywhere to post a bug report. They can just send an email to e.g. ivan-support@googlegroups.com. Or if we register this attnam.com domain with Google Apps for Work we can get an address like ivan-support@attnam.com. What do you think?

I think the biggest reason for this is that the angel has a really good weapon skill + accustomization on that weapon. Whereas an adamant golem only starts with level ~4 unarmed skill. And also the dex/agi thing as Batman? mentioned.

So you'd have to first train your golem's unarmed to increase it's damage per hit.

Yup, it's just a matter of finding one that doesn't conflict with IVAN's existing style too much.

Some that I've enjoyed reading are the JSF Air Vehicle (really extensive), LLVM (compiler) and Juce (audio engine) coding standards, and the EECS 381 course material, to name a few.

While these are really good for general (C++) programming style and best practices, they might clash with IVAN's existing style in some areas. To cover that we could make a minimal list of things that are "unique" to IVAN, and for all other more general stuff refer to some external coding standard.

The player is still free to take advantage of stacking multiple ghosts with good items on a ghost-generating level so there's that. Or is there a limit on how many ghosts a level can have?

Yes, those, no tabs, and any other consistencies we can find in the original source code, off the top of my head:
* no braces for 'if's, 'while's, etc. if they contain only one statement
* no space between 'if', 'while', etc., and the following '('
* 'lowercasewithoutunderscores' for type names, 'PascalCase' for variable names
* no space between type name and '*' / '&' in variable declarations
* comments start with a capital letter

There are also some inconsistencies that we should probably fix. For example sometimes '&' and '|' have no space around them but there's also lots of code with spaces around them. I think they're more readable with spaces.

Maximum line width? There are some ridiculously long lines that don't really contribute to readability. Would something like 90 or 100 be good? With 90 I can fit two pages of code side by side in my editor which is really handy.