Let me know what you think.
Also, if anyone wants to check out the source code, it’s posted on my Bitbucket account, and licensed under the MIT License (the graphics/Javascript have various licenses, and are documented on the Credits page).
]]>The big thing to note is that BZFlag 2.4.x is not compatible with BZFlag 2.0.x. You cannot use a BZFlag 2.4 client on a 2.0 server, nor can you use a 2.0 client on a 2.4 server. Servers will slowly upgrade to the new version, and some may run both versions of their maps for a while. There will be a transition period of several months. Windows and OSX users will be able to easily keep both versions of the game installed and in use. Linux users will have to do a bit more work for that, but it’s still possible.
Server owners will have to make some minor changes to their configuration files for BZFlag 2.4. They will also have to update any of their third-party plugins to the new BZFS API format. We have documented the upgrade procedures here:
http://my.bzflag.org/w/BZFS_2.4_Upgrade
http://my.bzflag.org/w/BZFS_API_2.4_Upgrade
Some of the major features include:
Check out the ChangeLog for more changes.
Here are the downloads:
UPDATE: The Mac OSX build is now up!
]]>Find out info about the beta on the BZFlag forum thread.
]]>Now the plan is to move trunk (2.99.x/3.x.x) out of the way, copy v2_0branch (2.0.x) into trunk, and then relabel the new trunk as 2.3.0.0. Then we’ll start to bring back specific low-risk features from 2.99.x and put them into 2.3.x, which we’ll release as 2.4.0.0 (or whatever we decide on). The idea is to push for getting a release out in a month or so. This will mean there is less time for feature creep to take over again, which in turn will reduce how much testing we have to do. Less new features = less chance of breaking stuff.
It won’t be BZFlag 3.0, but it will be a new version that has features worth upgrading for. Here’s a wiki page that we’re working on that covers the plan: http://my.bzflag.org/w/BZFlag_2.3
We’re also going to work on migrating all of the web services (forum, list, wiki, main site, etc) to a different server that will be a bit more … responsive. The existing server has been less than ideal for a long time and has hit various resource limitations. It’s not that we’ve outgrown the server, but there is just a couple resource hungry processes (coughirssicough) on the old server that chew up lots of RAM (hundreds of MB) and make everything else very slow.
So, I’ll be working on the migration over the weekend here. During that time, there might be some temporary outages.
]]>Here’s some additional features that I might add in the future:
Note that it does use a couple files (and will soon use more) from another open-source project of mine called mvcish.
]]>I’m going to keep adding some features and I plan to release the source code for it. Also, I currently don’t have it set to update automatically, so it won’t reflect changes at the moment.
Examples of things I might/could add:
If anyone else has ideas of what I could add, let me know.
]]>Instead, it’s just a heads up that there will be some temporary server downtime coming up. First, I’m transferring my domain name to a new provider, so that may cause some issues already. I’m also moving to a faster server, so I will have to shut down the old instance of bzfs and bring it up on the new server. This will have a new IP address, of course, so it may not show up for everyone immediately. (DNS propagation, and all that..) I will do my best to make it as painless as possible for the players.
I’ll try to get some more useful information posted here again. Life has just been busy lately, so I’ve had less time for this.
]]>
Emailing reports
I have a little script that I use to email reports that people leave on my servers. A report is left on a server by hitting a chat key, typing /report, and then after that the message the user wants to leave. Generally, it is necessary for the admins or owner to join the server and run /viewreports to see what reports have been left. However, with this, reports can be emailed to any email address. You could set up a mailing list for your top admins so that they receive these reports. Here is the script:
#!/bin/bash read read report #we want the second line, which is the actual report (echo $report | mail -s 'Report from '$1 $2) &
Chmod this to be executable (chmod u+x emailreport.sh) and make note of where you save this file. To use the script, you will add a reportpipe to your configuration file pointing to this script.
-reportpipe "/path/to/emailreport.sh SingleWordIdentifier EmailAddress@Whatever.com"
(Note that it should be a single line… the width of the blog makes it wrap to two lines) The first argument to the script is a short single word identifier. This could be the port number, a short name for the map, or whatever you want. It will appear in the subject line of the email as “Report from SingleWordIdentifier”. The actual report (including who it was from) will appear as the body of the email.
Watching a log in real time
There are times when I get bored, so I check out what’s happening on my server by reading the chat and server messages. I run the logDetail plugin, so I get messages formatted a certain way. I can keep tabs on the current chat messages (and server messages, commands, and reports) by using this command:
tail -f -n 500 log | grep MSG
The tail command is used to read a number of lines from the end of a file or piped output. In the case above, it reads the last 500 lines of the file named ‘log’, and then continues to “follow” the file via the -f option. When it follows the file, it means that it keeps reading any new lines added to the end of the file. All of the output from tail is piped to a grep that looks for the word MSG in all caps, which is what the logDetail plugin will output for chat messages and other types of messages. By doing this, we can read chat and related messages in real time from the *nix shell.
I’ll try to cover some of my hosting layout in a future post.
]]>There’s a forum thread over at the BZFlag forum about this as well.
Downloads:
As I don’t have an Intel Mac (much less a Mac that boots) I can’t verify the OSX builds will work as noted, soooo…. have fun! :)
If you encounter bugs or problems, please check if they have already been reported. Here are some places to look:
And feel free to mention/discuss the bugs (known or otherwise) on our #bzflag IRC channel. If you want to help contribute any fixes, that is welcome as well.
Happy tanking!
UPDATE: Removed “Tiger” from the note for mrapple’s OSX build. Someone reported it didn’t work on Tiger.
]]>So anyways, if you didn’t know, BZFlag 2.0.16 (named “No foolin”) is out. Source packages and a Windows installer are available for download. An OSX package may or may not happen. There are a couple notable new features in the client. There are a few other minor changes as well.
First, you can use the mouse to control the view in observer mode. If you are in either tracking (tank or flag) or roaming mode (press F8 to cycle modes), you can click and drag the mouse to control the view. You can use the left, right, and center (press the mouse wheel) to move differently. You can, of course, continue to use the arrow keys paired with the modifier keys for observer movement.
The second is a new feature back ported from the development code called “shot length”. This gives the bullets a different look. They will appear to have a tail. You can enable this feature by adjusting the Options > Effect Settings > Shot Length setting. View the full post for screenshots of the new bullets, as well as talk about my April Fools prank.
Here’s a comparison of the new and old style.
A good number of you are probably aware of the April Fools joke I had on the server. It worked quite well. If anyone wasn’t on my server on the 1st, then you missed all the poorly typed sentences. I had effectively converted The AOLer Translator to a BZFlag server plugin. Anything that anyone said would get brutally converted into AOL speak. Here are some of my favorite parts (not in any specific order):
Burger King: Y MUST U BUTCHAR TEH 3NGLISH LANGUAEG
TASAIRES: MORE ADMIN!11!1!!1 LOL AND CHAT SARVER PROBLEM??!1!!111!!?!???!?!??! OMG LOL WHEN CAN FIX TAHT??!?!??! OMG WTF ;)
Blissarde: SI CAPS LOK ENABLAD ON DA SARV OR SOMETHIN?!!?! WTF
sleepyman: MAH TYPIGN SI BIGN CHANG3D ON SCREN
Animal Lover: MAYB IF I TYPE EVERYTHIGN IN CAPS 2 BGIN WITH IT WIL APEAR SMAL
Animal Lover: NAVERMIND
ekko.: AXCUES ME?!??!? OMG WTF
ekko.: WAIRD I DIDNT SAY TAHT
ekko.: WTH LOL
ekko.: SOMATHIGNS WRONG WIT MAH COMPUTER SORYY
think_tank: liar
ekko.: Y DO U THINK IM TYPIGN LIEK THES DUMB DUMB?!!!!??!! WTF LOL
genotronic: WUT SI HAP3NIGN I DONT HAEV CAPS ON BUT I SE AL IN CAPS
moonlight: IMM NOT WRITIGN THES IN CAPS BUT I DUNO Y ITS COMIGN OUT IN CAPS.!!1111!1!!! OMG LOL
moonlight: ALRIGHT SOMEONA HAEXD THES S3RV3R
Well, you get the idea. It was hilarious. It also made people say random things when they capped a flag, and all tanks spawned 4 units in the air.
]]>