When it comes to Vanilla Angband, who does what for the game?

[APWhite]

I'm just curious as to how many people are working on this game, and who you are and not least what you are contributing with for Vanilla Angband?

I maintain the code for the borg, which is a screensaver version and automatic player. The borg will play the game and you get to watch it. There are some configuration files that allow you to exert some influence on how the borg plays. The borg source and executable files can be found here. I work on the borg nearly daily, and make updates a couple times a week.

Most of what I do is try to keep the borg up to date with the changes to the game code as it goes through development. I add new features and change the AI a bit as I go along.

[Magnate]

I maintain the code for the borg, which is a screensaver version and automatic player. The borg will play the game and you get to watch it. There are some configuration files that allow you to exert some influence on how the borg plays. The borg source and executable files can be found here. I work on the borg nearly daily, and make updates a couple times a week.

Most of what I do is try to keep the borg up to date with the changes to the game code as it goes through development. I add new features and change the AI a bit as I go along.

Hi Andrew - I'm very keen to get a better handle on the Borg code, because I think it could really help us with finding and fixing bugs in the dev versions - but to do that it we would need to maintain a "borg" branch on github for continual updating and testing. Would you consider publishing the borg on github so we could do that? We wouldn't expect you to keep up-to-date with every dev version (but help would obviously be much appreciated!).

[buzzkill]

I'm not part of the dev team. Hell, I don't even play Vanilla. I'm one of the guys who has fond childhood memories of brutal, unforgiving rogue-likes and tries to take the maintainers to the woodshed whenever I feel they're about to step in it, that is, taking the game away from it's historical roots (into variant territory) or trying to force it to have a kind heart. I feel I've largely failed at my task, and have all but given up on trying to "Save Vanilla".

[APWhite]

Hi Andrew - I'm very keen to get a better handle on the Borg code, because I think it could really help us with finding and fixing bugs in the dev versions - but to do that it we would need to maintain a "borg" branch on github for continual updating and testing. Would you consider publishing the borg on github so we could do that? We wouldn't expect you to keep up-to-date with every dev version (but help would obviously be much appreciated!).

No, I don't mind it. I tried to set one up several months ago. But I don't think it worked correctly and I had a horrible time trying to find the time to teach myself the command line stuff for properly uploading the changes. If there were some more simple execution commands, or a GUI, or a macro.

You guys did a nice job with the thread ("trying to git get" or something like that). But at the time, I was working +70 hours a week setting up my new practice. Now I am only working +55 hours, so I could revisit the issue.

It would be a lot easier if one of you guys walked me through the process of setting up the proper branch, or did it for me.

It looks like I have gitBash and GitGUI on my machine, but I didn't ever get GitGUI to work correctly and always ended up with command line coding (Git Bash). As I recall, it was a problem with verifying the repository or something. I seemed like such a mess.

The other problem is the borg330. It does not work due to some changes in how the inkey() works. Tak was supposed to take a look at it, but he hasn't gotten around to it.

[Magnate]

No, I don't mind it. I tried to set one up several months ago. But I don't think it worked correctly and I had a horrible time trying to find the time to teach myself the command line stuff for properly uploading the changes. If there were some more simple execution commands, or a GUI, or a macro.

You guys did a nice job with the thread ("trying to git get" or something like that). But at the time, I was working +70 hours a week setting up my new practice. Now I am only working +55 hours, so I could revisit the issue.

It would be a lot easier if one of you guys walked me through the process of setting up the proper branch, or did it for me.

It looks like I have gitBash and GitGUI on my machine, but I didn't ever get GitGUI to work correctly and always ended up with command line coding (Git Bash). As I recall, it was a problem with verifying the repository or something. I seemed like such a mess.

The other problem is the borg330. It does not work due to some changes in how the inkey() works. Tak was supposed to take a look at it, but he hasn't gotten around to it.

Well then it's a win-win for everybody - takk is much more likely to get round to looking at it when it's on github and all the conflicts are easy to see.

I remember you tried before, and I also was pretty busy at the time. It's great that you're willing to try again - I'm really happy to help. Best would be to drop in on #angband-dev at irc.freenode.net if you can - even if I'm afk someone else should be able to help. Otherwise PM me and we can exchange IM details.

Just off the top of my head, the sequence is:

1. Get a github account and log in.
2. Go to http://github.com/angband/angband and click the Fork button.
3. On your command line, type "git clone http://github.com/myaccount/angband.git"

But if it gets messy, let's talk it through.