Multiplayer is gonna be a hit on Scratch, and I have a few ideas for it.
1. Client sided screens. You can't all share a single screen in an MMO game. So it should be easier to implement client-sided screens to users that only they can see and nobody else. It helps out game developers here on Scratch by eliminating the required implementation of split-screen. Another aspect of client sided screens is that you can use the same controls that everybody uses to control their characters with no conflict, so that you can control your own dude.
2. Server projects. Since multiplayer will most likely come out, the Scratch server is gonna be jammed with online games. This can amount to an issue, so it would be easier by having a running project used to run games internally. It can host multiple games, receive user sent data, match up players, etc. It can be useful for containing the data of hundreds of games, allowing in-game chat, inviting others to games, or ban somebody if they cheat. It would be very useful, and certain projects will look for this server or many more! How it would work is that it would share variables between clients, and store information for everything in games etc.
Offline
1. Explain further, please?
2. That's sort of how it will work, the difference is that there is no one project "in charge".
Offline
bobbybee wrote:
1. Explain further, please?
2. That's sort of how it will work, the difference is that there is no one project "in charge".
The client pretty much sends information to a "server", which manages what players do, and the "client" shows what happens from your point of view. If the center of control was a single project, there would most likely be player control conflict and view conflict, unless that's already solved and projects' clients work solo without it all being one single screen. The "server" would, in other words, keep it's usefulness by keeping game data like player position, direction, health, etc.
Offline