Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[MEDIK]

I added some stuff around client ID passing, and 2 players on the same server now work. 3 don't, for some reason I'll investigate, but that's secondary.

The main point is that we should now test it on a bigger distance than loop-back. I want to see whether it works on a real connection too.

OK, make it run without GUI and I can host a 24/7 test server

It's not even possible to run a server with GUI. 

WHAT!?

Why...

No host playing then?
Or the host needs to open another window to play?

[Orpheon]

Aww, and I just added the UUID to the list of known lobbies

Eh...We're probably going to use the standard gg2 one as soon as it stops breaking everything.

I added some stuff around client ID passing, and 2 players on the same server now work. 3 don't, for some reason I'll investigate, but that's secondary.

The main point is that we should now test it on a bigger distance than loop-back. I want to see whether it works on a real connection too.

OK, make it run without GUI and I can host a 24/7 test server

It's not even possible to run a server with GUI. 

WHAT!?

Why...

No host playing then?
Or the host needs to open another window to play?

"other window"? What other window? Atm, the server doesn't open a window at all, it doesn't even load pygrafix.
You host a server with one console, and join with another. For now, that's sufficient, seeing as much networking debugging still has to be done, and you need separate console for that.

At release, we'll make an option that'll start both the server and the client separately, and let you play with one click.

[Loler]

I hope this comes out soon.

[Orpheon]

Found the multiclient bug.

This

Code: [Select]

    for index in range(numof_players):
        player = engine.player.Player(game, game.current_state, index)

        player.name, player_class, character_exists = struct.unpack_from(">32pBB", event.bytestr)
        player.nextclass = function.convert_class(player_class)
        event.bytestr = event.bytestr[33:]should have been

Code: [Select]

    for index in range(numof_players):
        player = engine.player.Player(game, game.current_state, index)

        player.name, player_class, character_exists = struct.unpack_from(">32pBB", event.bytestr)
        player.nextclass = function.convert_class(player_class)
        event.bytestr = event.bytestr[34:]Spot_the_difference.jpg

[notajf]

Spot_the_difference.jpg

     for index in range(numof_players):
         player = engine.player.Player(game, game.current_state, index)
 
         player.name, player_class, character_exists = struct.unpack_from(">32pBB", event.bytestr)
         player.nextclass = function.convert_class(player_class)
-        event.bytestr = event.bytestr[33:]
+        event.bytestr = event.bytestr[34:]

[Rodoval]

Seriously
a single digit

Wow you guys have courage

[NAGN]

yes well its essential to unpacking, if you're just one byte off or on, then the whole game could crash

[Orpheon]

yes well its essential to unpacking, if you're just one byte off or on, then the whole game could crash

It's when it doesn't crash, but spawns a player a fraction of a second too soon and crashes the game 10 seconds later that it gets hard.

[notajf]

Seriously
a single digit

Wow you guys have courage

??

A single digit that's very meaningful.

[MedO]

Nice find! That kind of bug can be a nightmare to hunt down.

[notajf]

Nice find! That kind of bug can be a nightmare to hunt down.

Tell me about it.
I've spent literally weeks looking for bugs in my Minecraft server written in C.
Let's just say my coding skill when I wrote it wasn't good and dealing with networking in C isn't exactly fun.

[Rodoval]

Seriously
a single digit

Wow you guys have courage

??

A single digit that's very meaningful.

I have no experience whatsoever with coding, so to me yes it is very surprising that a single little digit can create such a glitch.

[notajf]

Seriously
a single digit

Wow you guys have courage

??

A single digit that's very meaningful.

I have no experience whatsoever with coding, so to me yes it is very surprising that a single little digit can create such a glitch.

It's splitting up a packet of data, which is rigidly formatted. If you split it at the wrong place, of course it won't work as it will read the wrong data.

[nightcracker]

Seriously
a single digit

Wow you guys have courage

??

A single digit that's very meaningful.

I have no experience whatsoever with coding, so to me yes it is very surprising that a single little digit can create such a glitch.

You could see it like this, say I am splitting this string:

Code: [Select]

1234aaaabbbb9876into

Code: [Select]

1234, aaaa, bbbb, 9876
But I mess up in the first thing:

Code: [Select]

123, 4aaa, abbb, b987, 6
Quite a difference huh?

[Dusty]

So, what exactly did that do to prevent multiclienting?