Hi there,
I have been searching around and asking some Trem colleagues for any stand-alone text-based console for Windows that allows you to use Tremulous commands to connect to servers, chat and everything but without all the 3D and graphics stuff, just a simple console so that you can see what's happening in the server and send commands or chat.
A friend of mine has it but for Linux. I also saw a post a few days ago where someone had implement the console for the Wii.
I have searched for any Quake-engine solution but no luck.
I am not the right person to develop such thing since my knowledge on this networking stuff is equal or less than 0 but I am pretty sure there is something there to connect to a server in text-mode only. Maybe through UDP or even MS-DOS/Telnet?
Can anyone point me to the right direction?
Or provide the link to a post talking about this for Windows? (sorry to duplicate if that's the case)
Thanks guys,
TheLuciferSausage
it doesn't exist for windows (cmd.exe doesn't provide the features needed to make the console code work on windows, and sdl gets rid of it on windows too)
If the demand is big enough, I'll slice an hour off my schedule and write a command-line PHP script for this.
Quote from: Syntac on October 29, 2008, 07:31:34 PM
If the demand is big enough, I'll slice an hour off my schedule and write a command-line PHP script for this.
it'll take more than an hour, and there's a 90% chance i would have to delete it because of how it works.
Care to elaborate?
http://sourceforge.net/projects/console/
Why not enable it on windows and just disable it by cvar. Then those with a real terminal can use it.
Also, cygwin comes with rxvt and xterm etc.
Quote from: David on October 29, 2008, 07:41:58 PM
http://sourceforge.net/projects/console/
Why not enable it on windows and just disable it by cvar. Then those with a real terminal can use it.
Also, cygwin comes with rxvt and xterm etc.
1) it's a bit of a pain to steal stdout/stderr back from sdl
2) convince the ioq3 devs.
That better windows Console you linked just spawns an instance of cmd.exe invisible in the background and reads the text from every x ms. If you set x too high it's choppy, and if you set it too low, then your skinned console starts taking up a significant chunk of your CPU. It's not really the greatest but it's probably the best that can be done. :(
Anyhow, it's not adding any features of the sort that kev would be talking about, unless skins and transparency are really vital to the i/o handling. :)