0.3.0 available! (was: 0.3.0_alpha5009)
- wrtlprnft
- Reverse Outside Corner Grinder
- Posts: 1679
- Joined: Wed Jan 04, 2006 4:42 am
- Location: 0x08048000
- Contact:
ok, made a basic fix, the code now looks if the previous color code it found would include the matched name, if it does it won't hilight it.
This can still get confused by "invalid" color codes, so "0x12340x56<nick>" would refuse to get matched and "0x12340x56789a<nick>blah" would get the text after <nick> (here "blah") in the wrong color.
Do we actually support anything like this? Maybe we could make the server check all incoming color codes if they only contain [0-9a-f] or 0xRESETT?
This can still get confused by "invalid" color codes, so "0x12340x56<nick>" would refuse to get matched and "0x12340x56789a<nick>blah" would get the text after <nick> (here "blah") in the wrong color.
Do we actually support anything like this? Maybe we could make the server check all incoming color codes if they only contain [0-9a-f] or 0xRESETT?
There's no place like ::1
Is aabeta down? It's not reachable under beta.armagetronad.net or aabeta.dashjr.org . Yes, the file list is now in SVN, but the binary files aren't, I'd still need to upload them. Luke's last comment on that was this:
http://forums.armagetronad.net/viewtopi ... 5661#65661
Anyway, even if I knew how uploads work now, the servers have to be up for that, right? So I'm just ftp-pushing the files to SourceForge where they can hibernate in hidden releases. BTW, should 0.3.0 be on SourceForge eventually?
http://forums.armagetronad.net/viewtopi ... 5661#65661
Anyway, even if I knew how uploads work now, the servers have to be up for that, right? So I'm just ftp-pushing the files to SourceForge where they can hibernate in hidden releases. BTW, should 0.3.0 be on SourceForge eventually?
- Lucifer
- Project Developer
- Posts: 8640
- Joined: Sun Aug 15, 2004 3:32 pm
- Location: Republic of Texas
- Contact:
Hmmm, I think we should have a development release on sourceforge, too, but make sure it's marked in BIG BOLD CAPITAL LETTERS that it's unstable or something like that.
Not a big deal for me, though, so if you guys want to just keep them on beta.armagetronad.net, that's fine with me. But if you want to call for a vote, my vote's to put them on sourceforge, too.
Not a big deal for me, though, so if you guys want to just keep them on beta.armagetronad.net, that's fine with me. But if you want to call for a vote, my vote's to put them on sourceforge, too.
I created a new armagetronad-testing package and put the files in there:
http://sourceforge.net/project/showfile ... _id=195927
That should be warning enough. Those browsing SF directly will usually know they should check the release notes before downloading something blindly.
http://sourceforge.net/project/showfile ... _id=195927
That should be warning enough. Those browsing SF directly will usually know they should check the release notes before downloading something blindly.
-
- Dr Z Level
- Posts: 2246
- Joined: Sun Mar 20, 2005 4:03 pm
- Location: IM: luke@dashjr.org
Fetched them all to armagetronad/distfiles-- someone please verify the MD5s and add them to releases.php
Code: Select all
cec26eac4ae2d31678001f091fa8ef98 armagetronad-0.3.0-1.i686-generic-linux-gnu.rpm
879e6a989071c10da3919b468ebad7ba armagetronad-0.3.0-1.src.rpm
6862834c17c2817d3de8ded0de40afd0 armagetronad-0.3.0.i686-generic-linux-gnu.package
fc93a606d6e41a9ff549b32a8e21a37e armagetronad-0.3.0.src.tar.bz2
2606c1e8ebadc01acf2d0398d302b447 armagetronad-0.3.0.src.tar.gz
28f2a5e41af69aa898f65cc1f5daea6b armagetronad-0.3.0.src.zip
547305caa0297401549b575b477e1666 armagetronad-0.3.0.win32.exe
cc3b4e249753363c235f7643e86203ab armagetronad-dedicated-0.3.0-1.i686-generic-linux-gnu.rpm
82c7a65ad4048bfb733dcbc0cf22c046 armagetronad-dedicated-0.3.0.i686-generic-linux-gnu.package
804aab9a3dc0d4fed17caeb746c0e7b3 armagetronad-dedicated-0.3.0.win32.exe
-
- Dr Z Level
- Posts: 2246
- Joined: Sun Mar 20, 2005 4:03 pm
- Location: IM: luke@dashjr.org