And forums are back!
Wednesday 27 May 2009 at 9:19 pmI decided to stick with PHPBB3, but coded in an anti-spam question. If you can’t figure out the answer, you probably shouldn’t be trying to register an account…


I decided to stick with PHPBB3, but coded in an anti-spam question. If you can’t figure out the answer, you probably shouldn’t be trying to register an account…
...but should be back in the next few days. Something other than PHPBB. Sorry to kill your collective buzz.
The Zachtronics Industries Forums are now live!
http://forums.zachtronicsindustries.com
Feel free to go do forumsy stuff there, but be sure to keep it classy!
It’s been nearly a month since the end of the Design a Game for Engineers challenge and I haven’t said anything about it – what’s up with that?!
I received a total of 12 submissions, all of which were more or less decent ideas. Some stood above others in terms of whether or not they seemed like tenable projects, and a surprisingly large amount were similar to ideas I’ve thrown around in the past, such as traffic intersections, cellular biology, robots, and Pulse-like shooters.
For a while I had a side project going on that would have led to making some of these games, but we stopped when it was determined to be a stupid idea. I may contact some of you in the future, however, to see if you would like to collaborate should an opportunity arise.
Infiniminer is now officially open source!
http://github.com/krispykrem/Infiniminer/tree/master
I’ll be maintaining the official branch, which I encourage anyone who wants to help out to submit to instead of simply forking off into oblivion. Bug fixes will be taken after being code reviewed, but gameplay fixes will have to be discussed first (#infiniminer on Freenode). I realize that many of you have ideas for how you want to tweak gameplay, but we’re first going to have to figure out a sane way to allow for customizable servers without having loads of possibly conflicting server config flags.
GitHub uses git, which is a distributed version control program. To submit a patch, you’ll want to fork the official branch, make your changes, test them, and then use the GitHub interface to file a pull request to me to pull the changes from your branch into the main branch.
If you find any bugs or encounter any more crashes you can go ahead and submit them to the official issue tracking list.
There are two ways to fix the AllocateFormatAndData() bug as of v1.5:
Infiniminer v1.5 is now out, available here.
This is probably the last major update for Infiniminer.
Infiniminer v1.4 is now out, available here.
Infiniminer v1.31 is now out, available here.

That’s right boys and girls – Infiniminer is now available! To play, you’ll need the installer below, the XNA 3.0 runtime (linked below), and maybe the .NET 2.0 runtime (linked below, although you probably have it).
Download Infiniminer v1.5 [1.45 MB]
Download XNA 3.0 Runtime
Download .NET 2.0 Runtime
There’s a README with some basic information, although you can find everything there is to know by holding F1 while in-game. Keep in mind that this is a networked multiplayer game, so you won’t have a lot of fun playing it by yourself.
Make sure you configure your client (name, resolution, etc) by using the “Edit Client Configuration” shortcut, which can be found under the Zachtronics Industries folder in your Start Menu after installation.Fixing the AllocateFormatAndData() Crash
Open Source Project Information
Thanks go out to Chris Gengler (tayrtahn@gmail.com) for helping with the artwork.
The official IRC channel for Infiniminer is #infiniminer on Freenode. You can easily join by using this java IRC client, which will take you automatically to the channel.
I’m spinning up on a project related to the Games for Engineers series that, if everything turns out, will take it to the next level. What does this mean for you guys? It means it’s CONTEST TIME!
All submissions should be emailed to me at zachbarth@gmail.com by April 30th, 2009. If you have any questions, feel free to contact me by email or in the comments.
There was a “feature” in the textile formatting code that replaced an ‘x’ surrounded on both sides by numbers with an ‘×’, which is the unicode multiplication character. This, of course, broke every save-code that contained this pattern, as the two characters are very much not the same when the code is decrypted. This formatting was only applied when rendering the page, though, so in disabling the functionality all previously broken save-codes posted in the comments should now work.
Thanks to Jen for figuring out what was going on!
IT MEANT THAT IT IS GAME TIME!
