NexusServer v2 (C++/Qt)

[Aerospark]

I've been testing it out and it's awesome! Still a lot of work that's needed but it's quite the thing! I'm excited! :D

:o thanks for checking it out. Yeah it's still really early in development but it's progressing a lot faster then the original server.


Another update to the server:

I've started implementing posters, and I've implemented spaces (wallpaper/floor). I've also fixed a few bugs with furniture and the catalog/the hand.

Here is a list of the changes:
-Fixed a few bugs
-Implemented spaces
-changed default floor/wallpaper to match the old retail style
-Fixed the hand (from spaces dev)
-Started implementing furniture DB saving, and fixed posters in the catalog
-User data is now saved to the DB when a user disconnects.
-Implemented opcodes: Opcode::RequestRenovate, Opcode::RequestEnterCreatedRoom
-Updated database structure in a few places

[Liam]

Wouldn't be better to code in C# rather than C++?

[Quackster]

Nice Aerospark :D

What was the hand problem?

Wouldn't be better to code in C# rather than C++?

Wouldn't it be better if you didn't talk at all and you were grateful?

[Aerospark]

Wouldn't be better to code in C# rather than C++?

Actually no, quite the opposite. (IMO) One of the main reasons for making this is to use C++. It's more efficient, native, and multiplatform. C# on the other hand runs on top of a virtual layer (.NET, not native) and only supports Windows (with the exclusion of mono.) It is a powerful language, but it's definitely not better than native.

Also, using Qt on top of C++ allows me to program multiplatform implementations natively, without need for platform specific code. It also allows me to utilize Qt's SIGNAL/SLOT system, which is a really good way of doing safe cross-thread calls natively.

Nice Aerospark :D

What was the hand problem?

Thanks :) The hand problem was an issue that was created when I started implementing posters/spaces. Non-poster/space items would show up as PH boxes in the hand. The server was sending the type flag incorrectly.

[Aerospark]

New update:
I've implemented posters, and fixed them in the catalog/hand, I've also converted some misc stubs into properly implemented packets, and added some new ones.

Here is a list of the updates:
-Credits are now updated when purchasing items (but not changed)
-Implemented sending poster data when you enter a room
-Fixed the catalog
-Implemented purchasing posters
-Implemented placing posters in a room
-Clients are now told when a user leaves the room
-Implemented Opcode::RequestPosters
-Updated furniture placement packet to understand posters

Here is a screenshot showing posters: http://filebeam.com/55858e47f9c8ac98...453cbd5ef0.jpg

The testing server has been updated to the latest revision aswell.

Also, there is currently an issue with room creation--
The server crashes if you click "enter room" after creating a room, I'm not sure why, but until I fix it just click cancel at the end and then own rooms and it should work.

[Aerospark]

New revisions!
I've fixed the room creation crash (though it's still not quiiite right yet with the client,) and I've fixed/implemented some more things that needed work.

Here is a list of the updates:
-Fixed hotel view disconnect crash
-Fixed room shifting (entering a new room while in one)
-Fixed room creation crash (but it's still not proper)
-Users will now be placed at the door when they enter the room.
-Fixed the "under" furniture/walls issue caused by doors
-Proper player locations are now sent when you enter a room
-Made warping pay attention to the heightmap
-Room furniture is now saved to/read from the DB when a room is unloaded/loaded.
-Furniture in a user's hand is now saved when they disconnect, and reloaded when they log in.


The testing sandbox has also been updated to r123. There shouldn't be any more crashes. (Though I still need to code better crash handling...)



Oh also, though I have fixed the room creation crash, it's still a bit buggy, sometimes the enter room button doesn't appear, and if it does while you are in a room, you will enter a broken version of the current room if you click it. I know what's causing this, but I haven't had time to fix it yet.

[Aerospark]

Another update:

I've implemented picking up items, and posters, and fixed some issues. Also, the NexusTools server (svn, website, forums, sandbox server) seems to have disappeared. I'm not sure whats going on with it but it should be back up soon.


Until then, here is a list of the updates:
-Fixed the "Furniture is loading..." box if there is a poster in the room glitch
-Implemented picking up items
-Implemented picking up posters
-removed bool wallitem from Furniture::Furniture, it is now handled on init
-Made furniture handling more efficient. the type handling was hackey for posters (if(pnt->type=="I") -> if(pnt->wallitem))
-The hand now properly updates when placing paint/flooring
-Cleaned up the opcodes
-Fixed female figures in the console search
-Users are now properly removed from the online users list and deleted when they disconnect
-Started implementing friend requests

[Aerospark]

The NexusTools webserver, svn, sandbox etc should be back online, and I've committed the updates in the previous post. (There are also some misc bug fixes in there)


I've been a bit distracted with other things lately, and with the webserver being down, but development should resume again over the next few days.

[Aerospark]

Another update:

I've fixed a few bugs, and started implementing some of the pathfinding logic. I've also implemented a temporary "fuse string" system, this allowed me to implement things like waving and carrying drinks (temporary, incomplete)

Here is a specific list of the updates:
-Implemented temporary fusestring system
-Implemented waving (incomplete)
-Implemented drinks (incomplete)
-Implemented proper rotation on warp in prep for pathfinding
-Started implementing room modification
-Implemented room searching
-Implemented opcodes:
Opcode::RequestCarrayItem, Opcode::RequestWave, Opcode::RequestModifyRoom and Opcode::RequestSearchRooms
-Committed updates since server downtime

The testing sandbox has also been updated to revision 137.


Sorry development has been slow lately, I've had a lot more "on my plate," but I don't plan on stopping development on this.

[Near]

I missed your updates already! Great! Keep it up mate! Also, the fuse string system, how does it work? Sounds interesting.

[Quackster]

Wow, no one cares about this at all! It's very sad.
How's it going?

[Caustik]

Did you look into epoll() for async sockets in Linux, or are you using qt libraries?
I tested out the server, ran extremely smoothly
Posted via Mobile Device

[1ntel]

Actually no, quite the opposite. (IMO) One of the main reasons for making this is to use C++. It's more efficient, native, and multiplatform. C# on the other hand runs on top of a virtual layer (.NET, not native) and only supports Windows (with the exclusion of mono.) It is a powerful language, but it's definitely not better than native.

.NET and Qt are both frameworks... C# can be compiled for other platforms using Mono, of course C++ can be compiled for other platforms easier because it has more support than C# does for being compiled on other platforms like linux etc.. You can write plain C# without .NET but then you loose a lot of things you probably use from .NET.

[Muffmuncher]

Project dead? Damn, was checking everyday since the first version :(

[Aerospark]

Project dead? Damn, was checking everyday since the first version :(

Actually this isn't dead, I've just been busy lately with IRL stuff and other projects. I've still been writing little bits of code though, and hopefully development will speed up again in the future, I don't plan on dropping this.

The next update will hopefully be to the console, to properly implement friend requests. I've also found a problem with the packet IO system, sometimes the reader can be broken if you send too many packets at once, though this isn't hard to fix.

.NET and Qt are both frameworks... C# can be compiled for other platforms using Mono, of course C++ can be compiled for other platforms easier because it has more support than C# does for being compiled on other platforms like linux etc.. You can write plain C# without .NET but then you loose a lot of things you probably use from .NET.

Yes, C# and Qt are both development frameworks, but there is nothing inherently negative about frameworks. However, C# (.NET) runs on top of a virtual machine layer (VM) similar to Java. Where as Qt is directly on top of C++, so it compiles to native code using whatever C++ compiler its set up for.

Both languages have their advantages, but as almost all other servers for this game seem to be written using either C# or java (or something similar,) I would assume the community would benefit more from new code rather then rehashed code.