Hi !
Featured games (90)
games approved by the League of Dukes
Games in Showcase (736)
Games in Android Showcase (223)
games submitted by our members
Games in WIP (813)
games currently in development
News: Read the Java Gaming Resources, or peek at the official Java tutorials
    Home     Help   Search   Login   Register   
Pages: [1]
  ignore  |  Print  
  Guidance question  (Read 1472 times)
0 Members and 1 Guest are viewing this topic.
Offline kapocris

Senior Newbie

« Posted 2009-12-29 20:10:32 »

Hi! So I was making this great air hockey game...and before I put hands to work at making the multiplayer functionality...I would like to ask you guys a couple of basic and simple questions for you that have a lot of more experience than me:

The game is simple...the player that creates the game acts as server side and the one that joins the game...client.

So...thinking as the client or server...Do I have to send my position constantly or only when it has changed? and Do I have to process one package at a time ? Maybe it would be better if every time a new package arrives at destiny,  a new independent and temporary thread is created to translate the message and apply changes if it is necessary. This way I can keep on receiving packages. The only problem that I see is shared variables...It would be a mess.

So what I am asking is a general recommendation...a pattern to follow...basic guidlines in a simple server / client game. The only thing that I have to send/receive are positions, but how would it be more efficent?

Thank you very much I'd appreciate any help, happy new year for those who can enjoy your vacation

p.d.: I'm using UDP.
Offline h3ckboy

JGO Coder

Medals: 5

« Reply #1 - Posted 2009-12-29 20:33:27 »

if you using UDP then you would want to send a packet with neccesary info(x,y, and anything else needed) to the server every x milliseconds.
Offline Xyle
« Reply #2 - Posted 2010-01-16 05:14:23 »

I've read it quite a few times on these boards and others, and I have instituted a similar system in a few of my own trials of just sending a keypress update to other players. If player 1 moves, then send that 1 keystroke or move change to the other players and let the other players machines move that 1 updated player. If player 1 stops moving, send that 1 change to the other players. It was also recommended to send position updates every so often also.

Using this idea worked pretty good for me.

Life is just a game, learn to play!
╬-YellzBellz Games!-╬ Cheesy
Pages: [1]
  ignore  |  Print  
You cannot reply to this message, because it is very, very old.

cybrmynd (124 views)
2017-08-02 12:28:51

cybrmynd (147 views)
2017-08-02 12:19:43

cybrmynd (142 views)
2017-08-02 12:18:09

Sralse (158 views)
2017-07-25 17:13:48

Archive (629 views)
2017-04-27 17:45:51

buddyBro (737 views)
2017-04-05 03:38:00

CopyableCougar4 (1266 views)
2017-03-24 15:39:42

theagentd (1246 views)
2017-03-24 15:32:08

Rule (1221 views)
2017-03-19 12:43:22

Rule (1274 views)
2017-03-19 12:42:17
List of Learning Resources
by elect
2017-03-13 14:05:44

List of Learning Resources
by elect
2017-03-13 14:04:45

SF/X Libraries
by philfrei
2017-03-02 08:45:19

SF/X Libraries
by philfrei
2017-03-02 08:44:05

SF/X Libraries
by SkyAphid
2017-03-02 06:38:56

SF/X Libraries
by SkyAphid
2017-03-02 06:38:32

SF/X Libraries
by SkyAphid
2017-03-02 06:38:05

SF/X Libraries
by SkyAphid
2017-03-02 06:37:51 is not responsible for the content posted by its members, including references to external websites, and other references that may or may not have a relation with our primarily gaming and game production oriented community. inquiries and complaints can be sent via email to the info‑account of the company managing the website of java‑
Powered by MySQL Powered by PHP Powered by SMF 1.1.18 | SMF © 2013, Simple Machines | Managed by Enhanced Four Valid XHTML 1.0! Valid CSS!