vbGore Free Online RPG Engine

it would be easy if it is upgraded to vb.net...
because we can also apply our knowledge based from the vb6...

how naive :P

lol,dont want to argue...;p

Wooo C# ftw. Is it gonna use the XNA if it does you should make it 3D. Been learning C# for a while now doing quite well, make sure you learn OOP xD

I don't think we'd get very far without knowing OOP, let alone making a whole engine.

Nex has a lot of experience in OOP. I have quite a bit, probably not as good as Nex, but still take the time and care to refactor later when I notice the flaws.

OOPs my bad.

Har, in the event you and Nex can't handle a C# Port, I'd be glad to help you out </Smartass Comment>

Oh dear God, no. PLEASE don't use XNA. Too hard to make it install and work on other machines without having to install the entire toolchain. >_>

Yeah plus there's a few gray areas in the license.

To run XNA stuff, you just need a like 3 MB install. To develop with XNA is the only time you need the larger installation.



Like? Only hazy areas I can think of is when it comes to the 360 and using XNA's networking, neither of which are needed.

Oh I heard wrong haha, I thought you had to pay for a license to release it commercially. D: I smart!

Eh, I've heard of cases where people have had to install C# Express and XNA Game Studio to make their programs run, and dependencies are a pain in the ass anyway...

I would use SlimDX, a wrapper of DirectX for C# which uses the MIT license (I think), and doesn't use any dependencies besides the version of DirectX that the version of SlimDX you are using is/was built for. Google for it and look at it. It's teh shiz.

XNA can't be used to make Xbox360 games without a license, in the event that matters ;)
It is also a bitch for keyboard input (Was quite fast, had to add some filters and timeouts in so I didn't get 'hhhhhhhhhhheeeeeeellllllllllooooooooooooooooooo' when typing 'hello'), plus writing engines is too fun bypass the opportunity!

Also, I love the fact everyone ignored me :'(

Visual Studio is required for developing with XNA, which is a given since you have to have Visual Studio to do anything with XNA in the first place. The XNA SDK is needed for building assets with the content processor, which means that you have to either use that or find something else if you want to make a "game maker" type of thing where people can add their own graphics. But you can easily just not use the content processor. XNA is completely free in all shapes in form for PC development. For Xbox, you must have an active Creators Club to run non-commercial XNA games on your 360 for now. You must also have a CC subscription to sell 360 games, and they must be sold using the XNA Market or whatever it is.

So the limitations only really come into play when you turn to the 360, but even still, this is probably the most unrestricted system to ever hit a console. Compare that to Nintendo who will only give out the SDK for a huge fee to those who they have pre-approved, which is why there are so few companies who develop for the Wii / DS / etc.

Most people get mislead when it comes to the networking. XNA's networking system requires a CC subscription no matter if it is on the 360 or not. But there is no reason to even use XNA's networking for the PC, so that isn't a problem at all. But you have to use it for the 360 if you want networking, since the 360 doesn't support the System.Net namespace.

XNA has a trick up their sleeve, i saw it, it was an Ace of Spades!



Its probably because of your southern drawl. :)