Thread: send x,y-positions?

That would cause a lot of network traffic if you shoot often. I think you should tell the other computer where the bullet's been shot and the direction and let the it compute the next positions.
I've never actually done this, but it seems like it could work.

In answer to your second question, you could prefix the user and bullet with a keyword, maybe something like:

Code:

...
char [128] buffer {0};
char [128] temp {0};
//set prefix for the player data
strcat(buffer, "PLAYER ");
GetPlayerXY(temp); //this function should pass a char array into temp;
strcat(buffer, temp); 
send(hSocket, buffer, strlen(buffer)-1);//send the data

The other computer woudl receive something like: "PLAYER -10 5" for example. You should parse that to get what yo need. The shot could be something like:
SHOT PosX PosY DIRECTIONOFBULLET

Also, this should be in the networking forum.

hmm i made a small program and tryed it out
it works but not with bigger numbers

i did it like this:

Code:

#include <iostream.h>


#include <string.h>
#include <stdio.h>


 

void main( void )
{
	int  ch = ':';
    char string[] = "PL";

    char *pdest;
    int tal;
    int x=47;
    int y=65;
    int *px=&x;
    int *py=&y;
    int  klon=':'; 
    int *k=&klon;
    int result;
    char buffer[]="1234567890123456789";

 
	cout<<"string before "<<string<<"\n";
  
	strcat(string,(char(*))k);
	strcat(string,(char(*))px);
	strcat(string,(char(*))k);
	strcat(string,(char(*))py);

	

	cout<<"string after "<<string;


	pdest= strchr(string,ch);
	

	result=pdest-string+1;

	tal=strlen(string);
    tal=tal-result;

    cout<<"\nfound "<<*pdest<<" at position "<<" "<<result<<" with "<<tal<<" positions remaining";

    cout<<"\nx is "<<(int)string[result];

	strcpy(buffer,string);

    cout<<"\n this is buffer "<<buffer;
  
  

    pdest= strrchr( string, ch );
    result=pdest-string+1;   
    tal=strlen(string);
    tal=tal-result;
    cout<<"\nfound next "<<*pdest<<" at position "<<" "<<result<<" with "<<tal<<" positions remaining";

    strcpy(buffer,pdest+1);

    cout<<"\ny is "<<(int)buffer[result];


	///the output is PL:xpos:ypos   as i said i used the : to seperate them

   
}

does anyone know of a better way

ps maybe i did wrong to post this in this forum can a mod pls
move it to the networkforum if its in the wrong one..

not if you have timebased movement

So you're saying that if you had to send 5 megabytes of data every frame from a dial-up connection you won't have a single bit of lag, because it uses time-based movement? I was talking about lag, not the movement of the actual objects on screen.

edit: oh, yeah, and you misinterpretted yet ANOTHER part of my post. I said I wouldn't recommend the players' computer sending the data to the other players' computers. You had to try and be funny and focus on cheap humor, instead of reading my whole post. You DO NOT want to send the data in a p2p fasion. It is so easy to cheat it, it's not even funny. Oh, my bad, you probably don't know what p2p means, look up peer-to-peer on the internet. Use google.

your best bet is a client-server model.
once you make a connection to the server you'll probley only send a few messages to it.

your location, movement, and direction.
if and what your shoting.(i.e. your pistol or aka)
chat or admin commands.
and a very small BITE to signal that your stats has not changed.
like when you leave for a minute.

what you should recive from the server is basicly every thing from above for all the clients connected. including yours.
that be called a snapshot.
it be basicly a picture of everything going on at a given moment.

now there are many ways to optimize the snapshot for each client but if you get 100ppl in there then the processer overhead my be to much for the server.(advance topic).

basicly the snap will contain

Code:

{
    int Xpos,
    int Ypos,
    CVECTOR dir, //(x,y,z)
    int weapon,
    int StatusFlag //first bit ducking, second bit jumping,
                   // third bit running etc.
}

if you ask some for questions i might be able to help

[edit]
please note that only the origional author is a hacker. all the puck ass mother $$$$ers that use the software are called cheaters.

you can limit their effect but you can never stop an aimbot or wallhack b/c they work inside your restrictions.
you can check and make sure that the client is not trying to warp to a location by testing its 'pos' to know if it is a valid move.

never let the client manage its on health/armor/'weapons/ammo. that be what the server is there for.

never let the client send a message saging i killed/damaged 'player #id'

only let them send a message saying they shot in this direction.

if you do all that then the noobs who make cheats will give up for easier game. but there is always the poticheal for a pro to come in and mess with things. they usually only take a few hours for someone how knows what their doing.

read my edit

the easyest what is to phrase the incomming information on the socket. (tech example)

there are 2 easy ways.
the first thing you can send be a length. then you just read in that much information.
the second be by making a symble that will tell you that this be the end of the packet. one problem with this. if this symble is ever sent then it in the data and not at the end of a packet then your server will get confused and the data will get disjointed.


i usually make a large buffer and fill it/read it/ then flush.
fill it- get the length from the socket. MAKE SURE IT DOES -NOT- OVERFLOW YOUR BUFFER and then read in that much data from the socket.

you will have to send the data as structs. do not use points for they will not work at the other end. they only be good for the process on the machine they be created on. but you probleyy new that

readit - best bet would be to share a header file between you client and server code and then just
memcpy(YourStructerBuffer, FromYourSocketBuffer, sizeof(mystructer));
mystructer be declared in the shared headerfile. you could put it in 2 different files but that be messy when you need changes

what else?

[edit]
speaking of buffers. for now a char buffer will work. but an unsigned char buffer be the prober way to do it. mainly cause of the unsigned part.
someone correct me if i be wrong.
when you use just a char buffer then the first bit of each char will be set to 1. so if your going to read this in as in int/float/whatever then the information could be wrong and every 8th bit be set. that be a mouth full

sorry missed the meaning of that question.
it doesnt matter what type of buffer you want to send only that you know whats in it and can type sizeof(mybuffer) in the

send(socket,buffer,sizeof(buffer),flags);
statment.

im getting confused so i can send a struct instead of a const char?
i didnt know that was possible.
you wouldnt have any example code to show?

btw i have made aserver-client test program for my game

try it out

use the arrows to move
and be sure to open the one named spelserv first

ooops forgot to attach it see next post