Message Boards

What is your username and what does it mean?
My real name...

My other username, RTC_Marine reflected a time when I was with the TRTCC crew, Maonth suggested this nickname and I accepted it

What was the first doom you ever played? (Doom, Doom 2, Final Doom, Doom64, Doom3)
Doom shareware 0.99 iirc, the neighbor in the house next to us had a computer and we were around the same age, he introduced me to Doom, was good times :)

What was the first (unofficial) source port you ever played and when?
The first port I would have played was Doom 95, the first unofficial one was zdoom 1.22, I remember going crazy over the look up/down and jumping features

What was the first (unofficial) pwad you ever played and when?
Galaxia.wad was one of them, Crossing Acheron rings a bell too.

What is your favorite game mode?
Nightmare cooperative deathmatch, yes you heard that right :P nightmare respawning fast enemies + dming players. Just for the shear insanity of it

If you are in a clan, what clan and why are you in it?
I used to be in clan Unidoom, but the "used to" phrase is probably irrelevant in Ralphis eyes, since I bet according to him "There is no such thing as leaving UD"

What is your fondest memory of multiplayer Doom?
Wasting Blizzardson with rockets on Ralphis Magical Ice Forts and some UD clan matches

According to this page of your router http://bc.whirlpool.net.au/bc/hardware/?action=h_view&model_id=232 :

...Cisco does not support UPnP on any of their routers..

Spam? look at its signature

wow this is a really good job, nice work.

I found a couple of problems though, when you start the second map and go to the part to flip the switch (where you encounter the nazi) you can walk out the window and get stuck.

The other weird thing is unknown thing marker on the second map, you can see it in odamex, its through the other door at the start.

I think the layout of our server response packet structure could use a bit of organization for 0.5.

Code: [Select]

//--- Main Response
Tag - Unsigned 32bit Integer
Version - Unsigned 32bit Integer
Protocol version - Unsigned 32bit Integer

//--- Server information Related
Password MD5 hash - ASCIIZ String
Current map - ASCIIZ String
Time Left - Unsigned 16bit Integer

//--- CVAR Related
Cvar Count - Unsigned 8bit Integer
+Cvar name (Cvar Count) - ASCIIZ String
+Cvar value - ASCIIZ String

//--- WAD Related
WAD Count - Unsigned 8bit Integer
+WAD filename (WAD Count) - ASCIIZ String
+WAD MD5 Hash - ASCIIZ String

//--- Team Related
Teams Enabled - Boolean
Team Count - Unsigned 8bit Integer
+Team Name - ASCIIZ String
+Team Color - Unsigned 32bit Integer
+Team Score - Signed 16bit Integer

//--- Player Related
Player Count - Unsigned 8bit Integer
+Player Ping - Unsigned 16bit Integer
+Player Time - Unsigned 32bit Integer
+Spectator - Boolean
+Player Team - Unsigned 8bit Integer
+Player Color - Unsigned 32bit Integer
+Player Score - Signed 32bit Integer
+Player Fragcount - Unsigned 16bit Integer
+Player Deathcount - Unsigned 16bit Integer
You might notice some odd changes in here. They're optional, but here's why I did them:

* Now that we've made the team structure a little less hardcoded (with our teamsinplay cvar), we can treat the number of teams like we would number of cvars/wads/players. We should also be prepared if we want to make teams customizable to the server. (Custom names and colors... but CTF will still remain RED/BLUE)
* If it won't increase the size of the packets too much, I was thinking that the server could submit the color of each team and player to the launcher. I'm not sure if wx's Color (or Colour, it's very picky sometimes) supports RGB values, but it would be nice to support it. (Maybe add a color square next to the name a la the odascoreboard)
* Replaced player killcount with player score so we can use it for other game modes. Making it 32bit is overkill, I know, I'm just putting it in there in case we decide to further implement my "replace monster kills with damage inflicted" patch.
* I was thinking maybe we have player fragcount an unsigned value that doesn't decrease due to suicides and use player score for DM matches. (where it's the fragcount - suicides) Ralphis kinda doesn't like the idea of the scoreboard showing Score / Frags / Deaths instead of Frags / Deaths, so we could either disguise the scoreboard Frags as Score or make it optional to display Score / Deaths.

Not bad so far.

I think "Teams Enabled" is kind of irrelevant, since you can already use "gametype == teamdm" to determine if its enabled.

Also, "Team Name" is kind of the same, we can determine the name launcher-side by comparing "Team Colour" to a list of predefined values and set it.

Fragcount needs to be signed, this value can go into the negative if players keep dieing all the time.

Killcount should stay really, because we already have Deathcount anyway.

Oh and you forgot the player name field too. :P

It's a little more than just a "cosmetic issue".  Things that people may be used to seeing or not used to seeing when in certain maps IS a "gameplay" issue.  I'm not an expert on the subject but the argument could certainly be made.

For now I vote no on this until more research can be done.

I agree, stuff like this shouldn't be messed with, as it also may affect demo compatibility.

Its also bit non-sensical because someone may create a bug report to add it back later on.

Sorry but I have to vote no.

Yeah, one of the other ports ran into a fragmentation problem with packets stepping over the boundary if I remember correctly.

This sounds like a good idea and I have uploaded a (very) rough idea of an implementation:

Current list Format:
--------------------

4 bytes = Tag

2 bytes = Server count

Data block: 4 bytes (ip) + 2 (port) = 6 bytes

1) 10.0.0.2:10666
2) 10.0.0.2:10667
3) 10.0.0.2:10668
4) 10.0.0.2:10669
5) 127.0.0.1:10666
6) 127.0.0.1:10667
7) 192.168.0.1:10666
8) 192.168.0.1:10667
9) 192.168.0.1:10668
====================
8 ip/ports * 6 bytes = 60 bytes total


Proposed New List Format
------------------------

4 = Tag

Data block: 4 bytes (ip) + 1 byte (port count) + 2 (ports) = 7 bytes

10.0.0.2410666106671066810669127.0.0.121066610667192.168.0.13106661066710668
    4   1  2    2    2    2      4    1   2    2     4      1  2    2    2
====================
37 bytes total


What we do now:
1) We omit duplicate ips
2) We omit the server count field
3) We include a byte field after the ip, indicating how many subsequent ports exist

Pro's:
1) Saves data (example above proves a 23 byte saving)


Con's:
1) More complicated parsing required (but not much more)
2) We may or may not save space, especially if every ip address had only 1 port number

Hopefully my calculations aren't wrong, it is 2:30am.. :S

strange way to setup password in client, really..
and about versions server sends to launcher: what do all these numbers mean, for ordinary user? isnt it easier to setup normally readable version string and send it to launcher instead? that is "0.4.1 alpha" instead of 41 and 65 (never understood what is 65..)?

I can't ever remember why the protocol version was sent, it only deals with the client/server communication..

I just noticed that one of our resident devs decided to add an extra field into the launcher protocol without updating the documentation or telling anybody :/ the launcher protocol on the wiki has been updated, I'm sorry about this.

Deciphering the value is done by some macros in the source, I'll get to adding that later