Saturday, September 6, 2008
YMG 5K
My 9th-round opponent was a jerk: when I called a judge on a visibly bent card (which resulted in a match loss for an earlier opponent, and ultimately a warning for him) he was extremely rude/defensive until the ruling came back, at which point he actually shut up. He drew 3 Cryptics in game 2 which knocked me out of prize contention: a win in round 8 or 9 would have put me in 23rd at worst, I ended up in 43rd.
Still, top 20% (-ish). Nothing to sneeze at, and for the majority of the tournament I was kicking ass and taking names. Notably, my matchups were pretty mediocre throughout the tourny: played Kithkin twice (2-0), 1 Triple-tribe(0-0-1), 2 Five-color (1-1), 1 Kelpie (0-1), 1 Faeries(0-1), 2 Green decks (2-0). That's 3-5 bad matchups, or at least not favorable ones.
This tournament really reinforced a general observation about tournament magic: there are a relatively small number of douchebags playing the game and they tend to play slow, often painfully so. If they hadn't been so judge-understaffed (5, I think) I would have requested monitoring for slow play during at least the Triple-tribe game.
More general stuff:
*Faeries is really, really good. Like all kindsa good. Based on what I've seen of Shards, it will continue to dominate in Standard and possibly in Extended, as well. (ie, what I've seen of Shards is poopy)
*Shards appears to be aggressively multi-color, so I think there will be Karoo-ish lands (at common)
Tuesday, September 2, 2008
Emacs, TRAMP
TRAMP is an emacs extension that lets you edit remote files via ssh. This is nifty because it lets you have your own .emacs almost regardless of what you're editing.
Installation/use on Ubuntu is a snap:
sudo apt-get install tramp
add the following line to your .emacs (in your home directory)
(setq tramp-default-method "ssh")
C-x C-f /ssh:user@hostname:/path/to/file
(for whatever random reason, that syntax stopped working for me with no changes to the underlying system that I'm aware of after a week or so of using it. I got the error "ssh: ssh: Name or service not known" and revised the command to be as follows:
C-x C-f /user@hostname:/path/to/file
)
Tuesday, August 12, 2008
Honey Toast
Lorwyn-Shadowmoor Block Constructed has some number of decks. The number of decks doesn't really matter, however: the dominant archetype and the most powerful cards matter.
Faeries is probably the dominant archetype. If it's not, then it's probably mono-red. I don't care, actually. I'm not going to play either, although if I was forced to play one I'd play Faeries, simply because it has the best optimal draw essentially in the format. The problem with playing Faeries is that it's a completely known quantity: there just aren't many slots to adjust. Consequently, a skilled opponent can just play around it. With 2 god-draw games, that probably won't matter. But Faeries doesn't always get the god-draw.
Since I don't actually have the time, money or interest to test extensively, I decided to build a fun deck. A fun deck running as much of the power of the format as I could.
Initially, I played a deck with the goal of getting turn 2 Devoted Druid into turn 3 Overbeing of Myth. Without early disruption, I would win, period. The problem is that the format plays early disruption, so it actually makes sense to scale back and be more consistent. The one thing that testing that deck did tell me, though, was that Dream Fracture is good. Really good, in fact.
The way to make it even better is to have a deck consisting entirely of land and powerful cards. With such a deck, the card you draw off of it will almost certainly be better than the one your opponent just drew. A Quick 'n Toast basis seemed correct because of the average power level. The deck list follows:
2 Oona, Queen of the Fae
2 Primal Command
2 Hallowed Burial
4 Firespout
4 Shriekmaw
4 Cryptic Command
4 Dream Fracture
4 Broken Ambitions
4 Mulldrifter
26 land, configure to taste. my config:
4 Reflecting Pool
4 Vivid Grove
4 Vivid Creek
4 Flooded Grove
4 Island
4 Mystic Gate (2 of these are currently other filter lands in my deck due to a personal shortage of Gates)
1 Cascade Bluffs
1 Fire-lit Thicket
I don't know how it stacks up to the Chapin list, Justice Toast.
However, my thoughts:
I run more permission than any deck in the format except some builds of Merfolk, but Merfolk are not really fully on the radar AFAIK.
This means that when Faeries attempts a Mistbind Clique power-play, it's likely to result in their best creature hitting the graveyard, and I will either clash or draw a card, or choose a second cryptic mode.
I'm running fewer vivid lands than Justice, which seems correct: in my experience, I want at most 2 of my first 4 lands to be Vivid, and it'll happen to Justice almost every time. 3 of 4 is not implausible, which means no plays until turn 3. seems bad.
Archon of Justice is better in some sense than Oona, but unless Justice sticks a Runed Halo naming the Queen of the Fae, she will go the distance. If you untap with Oona, you win.
Basically, Honey and Justice take different approaches to solving a problem: Toast decks, despite their power, often just need to buy more time because of poor draws. I opted for a package that could take advantage of probably never missing a land drop, because Oona loves mana like I love bacon. Chapin included Mannequin to recur creatures, and it's very powerful. I don't think it is better than Dream Fracture, however.
getting Rails forms to be obedient.
The default Rails assumption is that you are doing things with ActiveRecord objects directly basically all the time. This is not a horrible assumption, but most of my Rails projects at LocaModa have not been "in charge", and so I've had to twist the expectations a little bit.
Most recently, I needed a form that was basically just a wrapper around a function that did direct inserts/deletes. Additionally, the form needed default values filled in. I'm a bad, bad man, and probably opened up a new level of hell for myself. But here's how I did it.
<% form_for :qux, :url => {:controller => das_controller, :action => das_action} do |f| %>
<%= f.text_field :foo, :value => @value %>
<%= f.submit "Suck it" %>
<% end %>
The Rails form_for docs are surprisingly opaque on this sort of thing, which I think is probably a mistake. Documenting possibilities, even the bad ones, is a very good thing, especially if the bad ones are accompanied with an explanation of why they should be avoided.
Tuesday, August 5, 2008
Heroku gem on Ubuntu Hardy
Getting it to actually work was surprisingly annoying: it error'd out very ungracefully whenever I entered a username/password, which turned out to be relatively easy to fix. command_line.rb (which lives in /var/lib/gems/1.8/gems/heroku-0.3.1/lib/heroku) needed to have a (require 'fileutils' ) inserted at the top.
With that problem solved, it complained about my ssh key (apparently vulnerabilities had been discovered), so I had to regen that. This shouldn't be a problem if you've generated your ssh very recently: mine was a few months old.
After that, it was basically just git annoyances. You need to (git add .) before a (git commit), which is best done as (git commit -a -m "your message"), which adds everything in the pwd (and recursively beneath) and then commits with a message, in this case "your message". Stealing blatantly from my older brother, I decided to make that faster to type and aliased (git commit -a -m) as gcm in my .bashrc. (alias gcm='git commit -a -m')
Monday, July 28, 2008
Rubygame
libsdl-ruby1.8 (probably not necessary, but might be useful if I needed an extension)
libsdl1.2-dev
libsdl-gfx1.2-dev
libsdl-image1.2-dev
libsdl-mixer1.2-dev
libsdl-ttf1.2-dev (this wasn't available for Hardy, so I did a package search and installed the package from Dapper)
Thursday, July 24, 2008
OGRE, ogre.rb
The current stable OGRE gem is 0.2 (and is named ogre.rb), and it wants ogre-1.4.4, which you can get reasonably easily by following the OGRE source installation directions and string-substituting appropriately. 0.3 is unstable and I was unable to install it on 64-bit Hardy.
I also needed to install osi-1.0.0, which is available on sourceforge. http://downloads.sourceforge.net/wgois/ois-1.0.tar.gz?modtime=1182593947&big_mirror=0 The installation procedure for that is directly analogous to the installation steps in the ogre install docs.
Additionally, I needed to muck around in the gem directory itself in order to be able to run any sample code. Specifically, plugins.cfg and resources.cfg needed to be moved into the gem root and resources.cfg needed /samples prepended to the path. The plugin folder needed to be /usr/local/lib/OGRE, although I think that I only needed to edit that because I had previously edited it on some wild goose chase.
With that, I was almost able to run the samples, but it resulted in a black screen that just wouldn't die. (Q, esc, C-c, CAD all failed) Turns out that I needed to adjust the settings: RTT Preferred Mode of PBuffer did the trick. (samples needed sudo to execute successfully) Exiting the rendering was accomplished via Q and arrow keys plus my touchpad allowed to to pan and zoom.
I'm not convinced that OGRE is intrinsically the way to go, but it certainly is getting the most attention from the Ruby community (the ruby irrlicht bindings are over a year old, and almost certainly out of date by now), and it seems like it would have a pretty strong symbiotic relationship with pyOGRE. Also, Google likes it enough that they gave it Summer of Code(rs). Rubygame seems like it might be too low-level, and Shoes doesn't seem capable enough at the moment.
As an interesting aside, Perl is apparently the best language for OpenGL development, running fully as fast as C. This raises a fairly compelling argument to have a compiler for a scripting language with a higher-level interface to OpenGL to target Perl for OpenGL apps. I may look into that project, as it seems potentially sexy as all hell.
The advantages that Python can currently cite for graphics dev over Ruby are largely documentation advantages, although Blender is also potentially a moderately big deal. Pygame is also probably somewhat more mature than Rubygame. That said, the incentives for using Python as a SDL API apply at least as strongly (and probably more so) to Ruby, so it still seems like a good route to go down if you want to do rendering/game dev using a high-level language.
If I end up using it seriously, I'll try to correct the heinous lack of docs.