Skip to main content

Matto3 and Matto4 *almost* make it to my favourite list

What I really enjoyed about FarCry was the stealth element. My favorite weapons are the sniper rifle and the silenced machine pistol. I enjoy well made maps, good atmosphere and well, stealth.

I hate "boss" fights, be they with "Bosses" or large numbers of enemies at the same time, out in the open. I also hate Trigens, but that's a good kind of hate.

So Matto3 and Matto4 almost made it for me, with Matto3 beating Matto4 except for the incomplete nature of Matto3's story.

Matto3: The good
  1. Silenced pistol with scope! Heaven!
  2. Lots and lots of humor scattered around.
  3. AWESOME maps. Really. Absolute top-notch crafting of textures, objects etc.
  4. Some innovative aspects, like shooting gas cylinder valves to turn them into rockets
  5. Some manipulation of the environment
  6. Multiple routes, to an extent
  7. Matrix style slow mo!
  8. No trigens

Matto3: The bad
  1. Incomplete - not really bad.
  2. Boss fight at a certain level
  3. No sniper rifle
  4. Jack Carvers voice acting. Sorry, even if I allow him to be British (quite suddenly, an ethnicity transplant as it were), that's not a native British accent.
Matto4: The good
  1. same as Matto3, except, see below.

Matto4: The bad
  1. Dude, where's my sniper rifle?
  2. Dude, where's my suppressed machine pistol?
  3. Dude, what's with all these Boss fights?
So, all in all Matto3,4 will appeal to most FarCry players, except those who want a stealth option.

Comments

Post a Comment

Popular posts from this blog

A note on Python's __exit__() and errors

Python's context managers are a very neat way of handling code that needs a teardown once you are done. Python objects have do have a destructor method ( __del__ ) called right before the last instance of the object is about to be destroyed. You can do a teardown there. However there is a lot of fine print to the __del__ method. A cleaner way of doing tear-downs is through Python's context manager , manifested as the with keyword. class CrushMe: def __init__(self): self.f = open('test.txt', 'w') def foo(self, a, b): self.f.write(str(a - b)) def __enter__(self): return self def __exit__(self, exc_type, exc_val, exc_tb): self.f.close() return True with CrushMe() as c: c.foo(2, 3) One thing that is important, and that got me just now, is error handling. I made the mistake of ignoring all those 'junk' arguments ( exc_type, exc_val, exc_tb ). I just skimmed the docs and what popped out is that you need to return True or...
Post a Comment
Read more

Store numpy arrays in sqlite

Use numpy.getbuffer (or sqlite3.Binary ) in combination with numpy.frombuffer to lug numpy data in and out of the sqlite3 database: import sqlite3, numpy r1d = numpy.random.randn(10) con = sqlite3.connect(':memory:') con.execute("CREATE TABLE eye(id INTEGER PRIMARY KEY, desc TEXT, data BLOB)") con.execute("INSERT INTO eye(desc,data) VALUES(?,?)", ("1d", sqlite3.Binary(r1d))) con.execute("INSERT INTO eye(desc,data) VALUES(?,?)", ("1d", numpy.getbuffer(r1d))) res = con.execute("SELECT * FROM eye").fetchall() con.close() #res -> #[(1, u'1d', <read-write buffer ptr 0x10371b220, size 80 at 0x10371b1e0>), # (2, u'1d', <read-write buffer ptr 0x10371b190, size 80 at 0x10371b150>)] print r1d - numpy.frombuffer(res[0][2]) #->[ 0. 0. 0. 0. 0. 0. 0. 0. 0. 0.] print r1d - numpy.frombuffer(res[1][2]) #->[ 0. 0. 0. 0. 0. 0. 0. 0. 0. 0.] Note that for work where data ty...
Post a Comment
Read more