How do you pick the game to mod?

To create a mod for a game, you must know the insides of a game.

Picked a game because i now how to develop for it... yup, that describes me pretty well.. xD

Picked a game I like, that I understand and that is missing quite a lot good features.

For me i always made a mod because i knew how to devolop for it making levels etc. Once you get more experienced though you choose a game to mod for features that are close to your mod.

I just love UT99, that's why I mod for it

Picked the game I liked. I picked Amnesia because it was an astonishing experience. Actually I was working on Penumbra, but no luck, then I moved onto Amnesia.

I don't mod, but it's a balence between knowing and what can do what I want. I know my way around hammer for example. I worked with UDK a little while because there was lots of documentation for it.

When I had delusions of making a colourful, power armoured themed FPS, I really wanted to mod Crysis (still do) because that has almost all the features I need already there. Maybe one day I'll go back to it. Who knows?

For me it usually kind of depends on the modding possibilities and the programming/scripting languages used. Of course I can, and will, learn new things but development will go faster if I'm already familiar with the languages used.

I would be the top three because those are the reasons I mod my favorite game (BF2 :D)

I pick the game that has the most open tools.

I'm not a modder anymore, if i do mod something. It's if i am unhappy with a certain thing in the game. Just like i did with C&C generals. Ai was crap, so i pepped it up :)

" 21% I picked the game I like most"

" 13% I pick the game which is closest to the mod I want to make"

That's scary!

Bring on the minecraft RTS and Freelancer FPS!

Nearly half the users on MODDB dont MOD. I found that funny, I actually find this site as more of a social kinda site, other than a db.

Well.. at least they know what a mod is .. there once was a time modders were considered nothing but hackers trying to take down the entire earths computer systems.

Should have added an answer "The game with the largest community support". I wouldn't fancy trying to jump into modding something with no videos/tutorials from the community to help me.

I picked the game because I know how to develop for it.

always mod a game you are passionate about

@Reborn:X

That may be, but often if you find a game very good and you like it and your a modder, chances are your gonna want to find out those insides...

I don't actually create mods as new game types,I'm just mapping,creating custom levels 'cuz I'm a noob in scripting and programing.So I've chosen Unreal Editor and Quake Radiant,first because I like UT and Q3,and also their mapping programs are easiest to learn,and can cooperate with a lot of other 3D programs also use 3D Max, Maya,and Blender.And at last if you learn Unreal and Radiant,you can mod for a lot of other games,because a lot of them are using Unreal and Quake game engine.Anyway with a little effort,almost anybody can revive their ideas and create cool maps.

1% for (I picked the game I like most) 128 votes and 2% for (I'm still deciding) 17 votes, what is wrong here?

I'm not a modder, but if I was, I'd pick the game I knew how to mod.

Not a modder, but I'd go with whatever engine with good mod tools that I know best. For me that's Source

All the first three answers, Source Engine. I absolutely love Half-Life and Half-Life 2, I wanted to map for a simple modern-era shooter (Counter Strike), and all it took to get started was 5-6 videos on youtube and the occasional visit to the VDC.

I pick the one that is easy to mod

Im not really a modder, more of a novice at the UDK.

Game I like to play and know how to develop for, that's why I stick to idtech3 & 4 as my fave online shooters happen use it and they aren't as saturated as other engines and games.

NOT A MODDER OH YEAH
:D

I choose games that I don't know how to mod.

i thought this was a porn site? damn

Goldsource is the simplest engine

The first three.

Not a modder, but if I were...probably would pick either first or third.

Would depend on a few factors, but yeah, first or third choices if I was a modder.

I'm a modder and from my point of view it goes like this.
I need to play the game sometime,and complete it,and then to try an existing mod for it.
If the game looks good with the mod,then i start modding it.
Did that way for STALKER COP,and still modding it...

Cant mod for beans :/

Know your engine! Know the limitations, know what it can produce, know what tools support its, know everything about it! However, best of all know its reliability. You don't want to spend many hours into one engine and then eventually coming to stops and bumps in your project. I took many leaps into engines and experienced the situations of not knowing my engine I work with. Do your research, it helps save your time and keep your project in a safe position!

45% of moddb are not modders...

oh the irony

i'd love to be able to mod, but starting from scratch is too hard without some help (proper help, not online guides)