Server Help

[Qndre]

IMPORTANT!!
This is a thread where I post the development status of my "Metaspace" client. Mr Ekted told me to start a new thread because the original thread "Spectate-Only-Client" now has 17 pages and people could think it's junk! Please read the blue description so you know what should be posted to this thread and what you should better post into the other thread.
_
DEVELOPMENT REPORT:
Sorry, I am a bit busy at the moment so development continues a bit slowly. But I keep working on it.
_
The idea of "Metaspace":
The idea of "Metaspace" (the client software included in the software package "SpecServ 2.0") is still the same as in the beginning of the development:

"Metaspace" should be a new Continuum client. It will be combined with my self coded webserver to make users (who don't have the Continuum client) able to spectate the game using their webbrowsers. So the program should recieve the data from the "Shanky Server", render it to an image file and send it to the browser there a plugin is running, which recieves the (very very compressed) image data from the server, decompresses it and puts it on screen, so everyone, who has a browser can spectate a game.

_
Things the client is already able to do:
- Connect to a zone and keep the connection alive (if sysop powers)
- Use VIE encryption to secure connection
- ACK reliable packets
- Display ships as windows which are moved around at the screen
_
Some of the next steps:
I must be able to calculate the path of objects which aren't discribed by position packets (bombs, bullets, etc.)! Then the renderer module must be expanded to be able to do more than just coordinate maps. It must include functions to blit images and transparent blitting would be nice. So it should generate a matrix with the internal 256 color palette of Subspace. Then there should be a function to generate images out of the dot matrix and put them together to a continuous videostream which should be MPEG compressed with two different bitrates and there should be an option to handle the bandwidth and to restrict how many people are spectating at which compression ratio. Then I must implement a function to blit the radar view on top of the spectate view (transparent blitting if possible) and finally a kind of GUI for the spectators and a remote-administration function for administrators is needed (for the remote-administration function the login data MUST be encrypted - I won't let a NOT-SSL-CONNECTION run).
_
What the future will bring:
A full C38 client integrated in a web server which can be set up by everyone and which can allow every user with a web-browser (even on linux systems) to spectate the game or the person who set it up to play and bypass bans. I do not want to cheat even if some people could abuse the source for it. The client should have a full physics engine, which I've already written and which already has been open-sourced by me. You can download it from the file being attached. Also important: This engine is still in beta.
_
Other stuff:
If some of you want to suggest some features or code, please add it here. If you want to discuss about the clients, why it should work, why not, if you think it's bullshit or if you think it's really a great thing please use the thread "Spectate-Only-Client" because this is a serious development thread so please don't chat here.
_
About the physics engine:
It is open-source! Feel free to use it in your own software if needed. It also supports 3D games (not only 2D games like subspace) and can simulate nearly all kinds of physics, like gravity, friction, no-energy-loose, ...
_
Catid (the famous bot-developer) about the physics-engine:

[Cyan~Fire]

Your source has a copyright (but invalid since it doesn't include a year) yet you say it's open source a freeware. Why not take that notice out?

Also, I would suggest re-writing it in C++ so most programmers can actually use it.
_________________
This help is informational only. No representation is made or warranty given as to its content. User assumes all risk of use. Cyan~Fire assumes no responsibility for any loss or delay resulting from such use.
Wise men STILL seek Him.

[Qndre]

Thanks. I took it out. It was there because the source should be included in an ego shooter network game (like half-life) which was written by some friends and me (I should write the physics). But after a few lines we recognized that the project was way over our heads so I decided to write it "open" (usable for every program, no specific function calls) and suggest it for Continuum.
_
I can't do C++ but the programming language it's written in is C-script so it won't be a problem to re-write in C++ for a good C/C++ programmer but I'm not good in C++. So if you are good in C++, you shouldn't have any problem in re-writing it because C-script (also known as WDL) isn't very different from C. If I knew the differences, I might be able to correct it so that you can directly include it in C++ but ... you know my knowledge in C++ is 0 (I don't know the basics, I don't know the further stuff!)
_
C-script is a bit simpler than C++ (maybe it isn't really but it looks simpler). So I used C-script to write the application. The differences between C-script and C++ are a bit like the differences between JavaScript and Java.

[Mr Ekted]

Your "physics engine" is about 1% of what's needed to handle SS physics.
_________________
4,691 irradiated haggis!

[Qndre]

[Mr Ekted]

What i am saying is that you need LOTS more code to handle just the simple physics of SS.

[Qndre]

That may be true! Even if the physics of subspace is very primitive.