User:PaulBlay

I'm currently working on XAngband, TinyAngband and now Angband/65. I also understand Japanese, so if you need anything translated let me know.

Angband/65 progress track:

• Mar 25, 2009 : 37 open tickets, 5 closed.
• Mar 26, 2009 : 38 open tickets, 7 closed. I'm starting to get to grips with how much stuff needs doing to get the objects all working right. Luckily the ticket system at the SourceForge page helps me keep track of what I'm doing but it's pretty heavy going.
• Mar 27, 2009 : 38 open tickets, 8 closed. I realise at this point that I could have done things quite a bit quicker with a different method, but that work's mostly done now. I've decided to rename the versions of future milestones to be a bit more realistic. (There won't be a proper beta release for quite some time).
• Mar 28, 2009 : 41 open tickets, 9 closed. Having something of a 'two steps forward, one step back' feeling. I am now officially impressed by just how much different Angband/64 was from the standard Angband of the time. Did you know that Angband/64 had random artifacts and an ammo equipment slot? I hope to get at least what I have ticketed for alpha done by that release. I will be subtitling the alpha release "Have I broke it yet?" as I doubt I'll have done much play testing (at all). However I do plan to release bugfixes as soon as possible if I get bug reports in.
• Mar 29, 2009 : 42 open tickets, 9 closed. Spent a lot of time comparing 'defines.h' in the two versions for clues as to what might need changing / implementing. This will probably end up generating more tickets later, but for the moment pushed most off into later milestone.
• Mar 30, 2009 : 49 open tickets, 11 closed. Found I made (what is probably) a classic newbie mistake - not enough testing between subversion commits. Am currently piecing back together from an earlier version using a merge tool. It looks hopeful that the damage isn't too devastating ;-)
• Mar 31, 2009 : 53 open tickets, 11 closed. Sorted out which bits were causing the trouble and re-integrated the rest ... and then went a step or two too far and broke it again. Oh well, shouldn't be as much bother this time around.
• Apr 1, 2009 : 58 open tickets, 11 closed. Now into the last month of programming before alpha1 release is scheduled.
• Apr 2, 2009 : Today I tacked the enormous task of making the flags compatible. It's not pretty, and there are probably hundreds of bugs to catch now :-(
• Apr 3, 2009 : 69 open tickets, 12 closed. Have decided to do an early 'pre-alpha' release in hopes of getting bug reports in ;-) Have shuffled many tickets down the milestones and added an extra alpha release milestone before the first beta release. Tentative date of first beta release remains unchanged.
• Apr 4, 2009 : Today I got somebody interested in joining the project. satofumi! Unfortunately I'm half-way through a big code update so the game isn't actually in a playable state at this revision. :-(
• Apr 5, 2009 : Checked another bunch of files for the big object flag update. I think one more day may do it (maybe two).
• Apr 6, 2009 : 67 open tickets, 16 closed. Finally finished checking all the files affected by the flag change. Changed version numbers to 0.0.1 and am preparing for preAlpha release.
• Apr 7, 2009 : 66 open tickets, 17 closed. It appears that the game will not run under Linux (although it will compile). Something wrong with object.txt? EOL differences? Anyway I'm trying for assistance on this one. In other news I have just 'caught up' with Vanilla Angband (that is I have implemented all the changes made to the SVN version since I started work on it). I'm still aiming for 10th Apr as the official preAlpha release.
• Apr 8, 2009 : 62 open tickets, 23 closed. Unfortunately it seems I have a nasty bug, probably related to mis-used pointers / arrays and probably related to keymapping system. I'm also attempting to switch over from Dev-C++ to Open Watcom for my compiler, but it is not an easy job.

As always anybody interested in assisting, would you please contact me. There is plenty of work for people of all levels of experience.