OT - Kind of

[Alpha Kodiak]

The hard part isn't the programming. The hard part is to come up with a complete, consistent game design including all of the rules, combat system, movement system, AI behaviour, etc.

Once you have the complete game design, you can begin the software design. I would recommend an object oriented approach to the design as it would simplify the implementation later. It is important to get the software design to model the game design completely. Pay attention especially to the data structures that you are going to use to model the game. Don't start coding until the design is complete.

As far as language is concerned, it is purely what you are used to. I would use C++ because that is what I use the most. It is not necessarily the easiest, mind you, just what I am comfortable with. Delphi would work, and even (cough... choke...) VB could be used. You want a language that can support objects and understands Windows dialogs, etc. (I am assuming you want it to run on Windows, rather than Linux, Mac, DOS or other operating system.)

The most important thing that most people overlook when approaching something like this is that the design is the important part. If you have a good design, implementation is much easier.
(Not trivial by any means, but easier.)