Welcome to my personal blog!
This is where I publish my thoughts and personal projects; please enjoy your stay and thank you for taking the time to stop by and pay me a visit!

Disclamer: By downloading, copying or using the software, source code and other files here provided, you accept the license you can read here.

Automatic login with MultiWars2

I’ve fixed an issue with the command line handling code in MultiWars2; you should now be able to correctly pass arguments to Gw2.exe.

As a reminder, this is how to automatically authenticate yourself when launching the game: MultiWars2LT.exe -email your@email.com -password yourpassword -nopatchui

About MultiWars2

I’ve released a new version of my Guild Wars 2 launcher, and I’ve renamed it to MultiWars2LT.

I have simplified it a lot compared to the previous release by removing both the debugger engine and the user interface. I have other projects I have to dedicate my time to right now (hint: tweet about ADis) and I currently don’t have much time to spare for MultiWars2. This is why I’ve rewritten it as a simple command line tool; I know it doesn’t have any fancy bell, but it should get the job done.

This being said, I will keep updating it in case compatibility issues arise with new patches.

Automatically tag functions with IDAPython

I’ve recently stumbled upon a nice IDAPython script from Alexander Hanel that automatically renames functions according to the APIs it references; I found it really handy, but I kind of disliked the fact that it was actually changing the procedure names, mostly because it was messing up the database when using verbose configurations (having too many tags meant having extremely long function names).

Other issues included the fact that adding and/or removing functions was not super-friendly, and that there was no support for profiles or different configuration files. Eventually, I’ve decided to write my own version of this small utility, trying to implements the following features:

  • Tag functions according to rules defined in separate configuration files
  • Use comments to tag functions, in order to avoid messing with names
  • Provide an easy way to uninstall the plugin, without leaving garbage in the database
  • Show the tags in a separate window

You can find both the Python script and the sample configuration on Github.

About VSync and Input latency

Are you still arguing about VSync and input latency? Leave me out of this! I don’t think I have the strength to talk about this once again.

Thankfully, a friend of mine just wrote a small article right on this subject, and I would like to share it with you; be careful though, the guy’s rude – and I can understand that: all his computers are malfunctioning.

A look at input latency and framerate
Alternate title: If you have a gaming mice and you play with VSync.. you are an idiot

DISCLAIMER You may (and should) know most of this stuff already. This is more of a “did you know” than a “Look what incredibly discovery I found”. To this day, there are people who say framerate doesn’t influence input lag, and people saying that their fast-paced game will be cool and popular and competitive even if it runs at 29.97 FPS. If you are one of those guys, welcome to the real and ugly world of input latency.

Our eyes are.. weird. Some people say that we only perceive 30FPS.. ish. It’s not really true, and there is not a real final number, as our central and peripheral vision are different (for example, it’ll take half the time to notice something that appeared on the edge of your vision than something that appeared in front of you). I’m not going to talk about that, there are already tons of resources that explore 60 vs 30 FPS, like this article or this website.

Today we’ll talk about getting the most high framerate for another reason: Input latency. First of all, though, let’s explore Hardware latency.

You can read the whole article here: http://blog.faulty.equipment/post/85541424684/a-look-at-input-latency-and-framerate

MultiWars2 update (version 2.0)

I’ve released a new version of MultiWars2, containing some bug fixes and many improvements. You can download both the binary release and (as always) the complete source code from the new MultiWars2 page.


  • Just a launcher: this program is just a launcher; once the game is started, you can close it.
  • Shared mode: use one installation and run it multiple times! If you only want to trade/craft/level up, then this mode is for you! Instances will not work though, and trying to enter one will crash your game.
  • Standalone mode: duplicate your game folder and run it normally.
  • Command line parameters: you can now set your preferred command line parameters for each profile you configured.
  • Avatars: each profile displays a unique and different image. Custom avatars are also supported, if you want to customize them!

Please report any bug you might find!

MultiWars2 – Identicon-like profile avatars

When you have several different programs in a folder you usually try to find what you’re looking for not by reading the name for each item but by looking at the actual shape and color of the icon.

I wanted this to work in MultWars2 as well, since power players might create several profiles for farming, playing and monitoring different worlds at the same time. I thought about using the Guild Wars 2 API, only to realize you can’t get any of the basic information about characters and/or players.

Instead of using user-configured images (no one would ever bother to add them) I choose to rely on automatically generated avatars and Identicon came up in my mind. This is a preview of what they might look like:

MultiWars2 - Identicon Avatars

I kind of like the first and the last one, but the two avatars in the middle? Those are pretty ugly!

New MultiWars2 version planned

MultiWars2 Beta

I just wanted to post a screenshot for the new version I’m working on. It’s nothing really fancy as you can see, but I hope the following new features will make up for my terrible skills when it comes to designing user interfaces:

  • Configuration files: you can now create several different profiles, each with its own settings. Thanks to this, you can now easily start each copy with a double click, instead of running MultiWars2 multiple times.
    Please note that this is still just a launcher; once you started your game, you can close the program!
  • Persistent configuration: standalone profiles will now save their own settings inside the game folder, so that you don’t have to reconfigure your client each time you start it.