Sounds like you're selling a model whereby all players just make servers and connect with people they know. That would be fine but there's one problem. Byond has been developed to appear it's capable of that, it even offers "Play, Join A Game, Host" but the problem is that anyone who clicks the host button needs to know how to portforward. ... playing it by themselves which is boring.

I don't see how your model works. It just means dedicated players will work it out and make a very small number of servers, basically your game with this model will go no where.

You can't expect players' servers to be better. But you can expect, within reason, to be able to purchase a better server.

Forum_account, your latest posts sound eerily similar to something I said awhile ago which you still decided to side against.

I can't determine if I actually got through to you or you're just flip-flopping your opinions for the sake of debating people. Just the other day you refused to acknowledge how some features are effected by lag more than others yet here you are saying it's a developer's own fault for making a game which doesn't run well on BYOND.

I sure wish I was more experienced in what BYOND is actually strong with.

Then again DM code itself executes extremely slowly

A decent interprented language like Lua

but they're not appreciating how much it already does for you. You don't really know what you're missing until you research how much work you'd have to put in just to get a basic environment up and running.

Graphics engine: you need to be able to see the game.

Sound system: to be able to hear sounds

Keyboard/mouse I/O

Networking: it needs to be secure, it needs to be fast, yet it needs to be accurate.

Development tools like a map editor

Native browser control w/ the ability to send "internal" links (or you'll end up with even more work as all the interfaces are in HTML)

The benefits you have from multi-threading

but how feasible it is to pull off.

You also have to facilitate a way for the client and server to be aware of a "map" and to know what to render. You'll also need to make sure that animations play properly and smoothly.

Simply being able to receive events is not what you need in order to make a game. You need to write your own event framework lest you end up with spaghetti code.

switch(msg) {
    case WM_MOUSEDOWN0:
        // find whatever was clicked and call Click()
        break;
    case WM_KEYDOWN:
        if(keyMapping[param0]) // assuming it's array of function pointers
            keyMapping[param0]();
}

The latter (requiring accuracy) is why TCP is required. But again, there is more to it than just being able to send/receive messages: you need an entire framework for this.

When a player presses a button on the keyboard, you need to be able to send it to the server. The server needs to send map updates to all the clients taking into account what state they're in.

auto client = FindSender(packet);
switch(packet_id) {
    case PLAYER_MOVE:
        for(auto &player : playersOnline) {
            if(distance(client.position, player.position) <= 6)
                network.send(player.address, client.id, client.position);
        }
        break;
}

How would you make sure that the player has all the required resources like icons and sounds? BYOND does this for you automatically by packing them into a resource file upon compilation and sending that resource file in the background to the client upon connection.

Not only do you need a map editor, but you need to define what a map is, and what the elements on a map are. This needs to be in a format that at least the server but most likely also the client can understand.

When you use a byond:// link within Dream Seeker it will automatically call a proc in BYOND. You'd need to copy this functionality or waste a lot of time redoing interfaces.

This tells me that you don't have much experience with programming outside of high-level languages like BYOND. Multi-threading is most definitely needed in a 2D game. Otherwise, how can I see what's on the screen and press a key at the same time? How can the server send the resource file to the newly connected client and not cause all other clients to freeze up?

// not an actual code, but very similar
while(true) {
    Message msg;
    while(ReceiveMessage(&msg)) // receive all message from Windows (input, etc)
        ProcessMessage(msg);

    Packet p;
    while(ReceivePacket(&p)) // not best interface, but looks nearly identical to previous loop
        ProcessPacket(p);

    UpdateFrame();

    DrawFrame();
}