Quake-III-Arena VS lychee.js

Quake III Arena

If you know C, you can check this out by comparing the different player movement code of Quake 3 and Quake 1.

You mean this code?

https://archive.softwareheritage.org/browse/content/sha1_git...

Do you see that notice at the top of the file? It says:

==

This file is part of Quake III Arena source code.

Quake III Arena source code is free software; you can redistribute it

The error messages comes from this file in the source code. It looks like the client is trying to parse entities from the server but the readcount is greater than the cursize in the messages. I am not an expert but I believe there could be a mismatch between the versions of your client and the servers you are trying to connect to.

After learning C, one of the first projects I came into contact with, was the ID Tech 3 game engine [1]

On the one hand, it taught me how professional C programmers structure their code (extra functions to remove platform differences, specific code which is being shared between server and client to allow smooth predictions) and how incredible fast computers can be (thousands of operations within milliseconds), but it also showed me, how the same code can result in different executions due to compiler differences (tests pass, production crashes) and how important good debugging tools are (e.g. backtraces).

To this day I am very grateful for the experience and that ID decided to release the code as open source.

[1] https://github.com/id-Software/Quake-III-Arena

Note that fair use as a concept (or prior art for that matter) only exist inside the US, not globally.

For example, I'm a European citizen and therefore the EU copyright directive of 2003 applies to me. Inside the European trade union, no legal entity and only human entities can own copyright. Legal entities such as companies can only own perpetual licenses, and contracts that give them the sole copyright usage and distribution rights have been nullified both in front of state level supreme courts and EU level courts a lot (Karlsruhe, Strasbourg, etc).

This also means that technically, if there's no warranty disclosure issued for automated code generation, the authors of the automated program are still responsible for any copyright infringement, legal damages, etc. which is a nightmare if it turns out the code was A/GPL'ed.

I'm just saying this, because there's a world of intellectual property guidelines outside the US, too.

Source: was sued for my lychee.js [1] project a couple times in the past, which was successfully generating composite pattern based codes that were trained based on ES/HyperNEAT hypercubes - also in the robotics/SCADA level factory sector.

[1] https://github.com/cookiengineer/lycheejs