Making games is hard work. It's like building a castle. If you come to the building site on the first day of the job and expect to single handedly build a beautiful castle with arched parapets and slender towers, you are likely to go away very disappointed and look back on a pile of rubble.
Game making is the hardest programming disciplin there is. Unlike in application programming where everything you do is triggered by something the user does -- clicking a mouse, choosing a menu, changing a window. While the application program otherwise sits quite idle waiting for input, a game has to do a lot, A LOT, of stuff in a few milliseconds. It has to show graphics, play sound, move the player, update every other animated entity in the area, and it has do do all that over and over again several thousand times a second because if it doesn't, then the game experience will be bad.
Game making is an acquired skill, and it takes a while to acquire it. I agree with Black Hydra in that you should lower your sights if this is your first attempt at game making. Don't worry about AI now. Don't even worry about FPS, because they're one of the hardest kinds of game to make good (and game making is hard enough as it is). Make a Pong, make a Pac Man, make an Arkanoid, and make a Tetris clone.
They are simple games, yet all the elements of games are in them: ai, game loops, sounds, graphics. And as you make them, you learn the craft, and you learn the skills required to tackle harder games. You become better. You learn what it takes to make a game, and at the same time the task is not so horrendously difficult as to put you off game making for good. So do 2d games before you attempt 3d ones. Make simple games before you try to make hard ones.
It takes time to learn game making.
Cheers,
Microman
-----
They SAID that given enough time a million monkeys with typewriters could recreate the collected works of William Shakespeare... Internet sure proved them wrong.
-----