lol hey there. well just so you know. don't expect to be creating anything of borderlands quality as a beginner. things like that take teams of people and alot of time. but yeah i would suggest unity. that would be the easiest way to get to where your'e going. start off with smaller projects and work your way up. lots of beginners make the mistake of starting too high and getting discouraged. I should know, as im also a beginner lol. But yeah, ive used unity before and its pretty solid. but i moved to c++ because i like the thought of building "from the ground up" and understanding whats going on so i can tailor my game engine to do exactly what i want. But if you're looking for an easy to use 3d engine then yes unity is definitely what your'e looking for.

lol hey there. well just so you know. don't expect to be creating anything of borderlands quality as a beginner. things like that take teams of people and alot of time. but yeah i would suggest unity. that would be the easiest way to get to where your'e going. start off with smaller projects and work your way up. lots of beginners make the mistake of starting too high and getting discouraged. I should know, as im also a beginner lol. But yeah, ive used unity before and its pretty solid. but i moved to c++ because i like the thought of building "from the ground up" and understanding whats going on so i can tailor my game engine to do exactly what i want. But if you're looking for an easy to use 3d engine then yes unity is definitely what your'e looking for.

Hey, thanks for the reply. Yeah I know that I can't even come close to what a full design team can do. I was just trying to reference the gamestyle I am going for. I do have some programming in my background, so I know it's a long road. I won't rule out designing smaller challenges if I can't get the concept right away. It's nice to remember your end goal sometimes too. That's one vote for unity. Happy holidays.

Please read this article first. Think about it for a while and then decide what you want to do.

Good read, thanks :)

Not sure if you read my OP or just skimmed it, but im working on game concepts at the moment and im initially planning a single player campaign. Let's say I stick with it and get some friends interested in a multiplayer option, I'm hoping at that point I can add the networking layer that would allow say 5-10 players. The game would be far from an MMO "massively" as the article points out. I only use the term mmo in the OP as a loose term to express character progression and the possibility of multiplayer. For the record I am very aware of the state of today's mmos and the fact that they are cutthroat to the point of most of them now having the free to play model. That said, the article should be relabelled from a financial standpoint because not every dev is in it to make money. I for one am just looking for a fun pastime. If I was in it to make money I'd avoid mmo like the plague, lol. Thanks for the reply.

I think unity and UDK would be good.

I Do have very small goals set in the beginning and as said before, if I can't seem to grasp the concept of certain code I am willing to use it on a smaller unrelated project until I get the hang of it. If a young developer is humble and not "cocky" I see no harm in keeping your eyes on the big prize so long as you realize its going to take awhile to get there. In fact I find that just by staying focused on what you want that gives me motivation to continue. I understand that alot of new developers don't realize how much work is needed and many even abandon their projects after failing to make the commitments, but I don't see anything wrong with a part time/hobbyist developer. If they are enjoying the creative aspects, it shouldn't matter if they choose to use an engine. Just my 2c and I'm not upset or anything. Thanks for all the posts. I'm going with unity and javascript until I get comfy with the engine. Then I want to go with the more verbose c#