I want to give a quick run down on a new game/community project I am starting.

The project is a mix between a PBBG/Neverwinter Nights/real time messenger/MUD. Players will create characters from a variety of classes and will be able to join or create a variety of rooms. Each room is basically a chat room with a twist. The chat room itself is a dungeon or a module/campaign that the players will go through. Some rooms are simple arenas that players fight random monsters and find random traps or treasures while others are a bit like a mud where they journey together through an entire adventure meeting NPCs, fighting monsters, disarming traps, looking for secrets, opening chests, ect.. All of this is done through a chat room like a messenger program. The monsters, traps, NPCs, ect will be entities but members of the room as well. The game will also encompass a Neverwinter nights feel by allowing the players to build their own rooms, monsters, chests, traps, modules, ect.. The room will guide the players through and challenge the players to fight together and solve all the problems of the campaign.

I have not named it yet. Chat Dungeon is just a name for now. I am not sure yet if I am going to stick with Javascript/Node.js or got with C# on the backend with something like SignalR. The front end will be browser based.

As an update I have test examples working with both Nodejs and SignalR. With the low cost of windows hosting now and teh ability to host .net apps on Linux I am thinking I may want to go the c# route. The elegance of C# classes and overall design always wins over JS prototypes and such.

Very cool idea! Although I will say I am not sure if I would want to go .NET Core. If all you want is the elegance of C#, you could always use Typescript for node. Pretty much everything you would want to use has a type definition. That aside, .NET Core is still working hard to move everything over from .NET FX to .NET Core. A ton of libraries and Nuget packages don't work for it. SignalR is not even officially released on .NET Core (although it does have a very functional beta release, since I believe it is coming in the Core release in a couple of months, but you would be starting with a beta version that could potentially change).

Really stick with it and give it a fair shot. This is going to be a very client-side heavy project and I think you will find the organization and the way you can nest components to be a breath of fresh air if you stick with it long enough to get used to it. No more piles and piles of jQuery events.