hi, so i started a thread about it, you know there are reliable and unreliable messages, i was wondering about some aspects of it:
1) reliable channel overflowed
it says "reliable", so it means to many reliable thingys yes?
what if you replace all reliable msgs with unreliable ones? like MSG_ALL with MSG_BROADCAST and MSG_ONE with MSG_ONE_UNRELIABLE ?
will it prevent this overflow or at least reduce "reliable channel"s stress? or will it work the same way before replacing?
2) difference between
MSG_ALL and MSG_BROADCAST ?
MSG_ONE and MSG_ONE_UNRELIABLE ?
i'm not pretty sure how does half life engine works and all that reliable and unreliable stuff, but i'd like to know that, like MSG_ONE_UnRELIABLE checks if user was put in server before sending unlike MSG_ONE, and there is one thing i worry about too "(could be dropped)" from description of MSG types in define, what can be dropped? O_o how?
PHP Code:
#define MSG_BROADCAST 0 // unreliable to all
#define MSG_ONE 1 // reliable to one (msg_entity)
#define MSG_ALL 2 // reliable to all
#define MSG_INIT 3 // write to the init string
#define MSG_PVS 4 // Ents in PVS of org
#define MSG_PAS 5 // Ents in PAS of org
#define MSG_PVS_R 6 // Reliable to PVS
#define MSG_PAS_R 7 // Reliable to PAS
#define MSG_ONE_UNRELIABLE 8 // Send to one client, but don't put in reliable stream, put in unreliable datagram (could be dropped)
#define MSG_SPEC 9 // Sends to all spectator proxies
__________________