Free quest helper software for linux

Xdebug Helper is a tool to start/stop debug with PHPs Xdebug extension.
The Xdebug extension helps you debugging your script by providing a lot of valuable debug information. The debug information that Xdebug can provide includes the following:
- stack and function traces in error messages with:
- full parameter display for user defined functions
- function name, file name and line indications
- support for member functions
- memory allocation
- protection for infinite recursions
Xdebug also provides:
- profiling information for PHP scripts
- script execution analysis
- capabilities to debug your scripts interactively with a debug client

Quest OpenSSH provides password-less, secure, encrypted remote login and file transfer services for Vintela Authentication Services (VAS). It is a derivative of OpenSSH, an open-source implementation of the SSH protocol.
Quest OpenSSH provides:
- default single sign on for Quest customers using VAS or VMX. Users are automatically and securely authenticated against Microsoft Active Directory using GSSAPI.
- compatibility with other SSH tools, including Quest PuTTY.
- integrated enhancements including high performance network support and TCPwrap access controls.
The software packages include both the client, ssh, and the server, sshd. Packages are subject to open source licence conditions.
Enhancements:
- This releases new features are the Match directive and inclusion of the HPN patches (High Performance Networking).
- Minor bugs fixed include NIS+ compatibility and improved service script reliability.

Aargh is a code generator, written in C++ and licensed under the terms of the GNU General Public License (GPL). It generates C++ code to parse a command line, using the getopt() facility available in UNIX and UNIX-like environments.
Automated Argument Helper project supports command-line options with integer arguments, string arguments, and no arguments. The generated code is commented and carefully indented for readability.
Its nice to have lots of command line options, but its a real pain to code for them.
Not that its difficult. Its just tedious, time-consuming, error prone, and no fun. I used to wince at the thought of adding command line options.
Not any more. All I have to do is define the options I want in a small XML file, and run it through aargh. Instantly I have C++ source code that I can compile and link into my program.
If I need to add another option, or otherwise change the rules, I can edit the XML and regenerate the code. No muss, no fuss. Now I can spend more time on the interesting parts of the project.
To use aargh, write an XML file to describe the options you want. When aargh reads the file, it generates two C++ files.
One file is a header that declares a class to represent the options. By default this class is named "Opts," but you can specify a different name. The other file is the implementation of Opts, or whatever you decide to call it. The Opts class provides member functions to parse the command line and return the results.
In your own code, declare an instance of Opts and call Opts::get() to parse the command line, passing it the argc and argv arguments from main(). Opts::get() returns zero if the command line follows the rules that you have outlined in the XML file, or non-zero otherwise. If the parsing is successful, the Opts object stores the results and makes them available to your program by a series of accessor functions.
Main features:
- You can enforce upper and/or lower limits on the number of non-option arguments.
- You can distinguish between options that take arguments and those that dont.
- You can specify that an option is required.
- You can require that the argument to an option be a non-negative integer.
- For an integer argument you can enforce upper and/or lower limits.
- For a string argument you can enforce upper and/or lower limits on the string length.
- For a string argument you can call a function of your own to validate the argument.
- You can allow multiple occurrences of the same option. In that case the generated code builds an STL vector to hold the arguments. By default the generated software allows only one occurrence of any given option.
Enhancements:
- You can now specify the location of the generated header file independently of its name.
- This feature may make it easier to incorporate aargh into complex build environments.

squid-nufw-helper is the authentication Single Sign On module for Squid, working with a NuFW firewall. The project allows for transparent authentication of users on a Squid proxy, even if the proxy is a "transparent" one.
Enhancements:
- This release adds an "-a" switch to pass the clients source port to htons() at will (this is required by some versions of squid, but not all).
- This release is marked as stable, as it has been extensively tested.

AA Helper Library is a basic library of helper functions for AAlib.

Inspiration that started this is AAJM, when I implemented circles and lines. More or less on a whim, I turned it into a more convincing project.

Yes, Im fully aware of the existence of libcaca. A few things:

1. Libcacas picture definition isnt as good as aalibs - as the designer of libcaca stated, its designed to make colors work right on ascii displays, rather than necessarily the shapes. For a simple example of this, run cacafire next to aafire on a screen at the same time

2. AA Helper addresses most of libcacas other good points - sprites and graphics primitives, primarily

3. If youre at the point where you feel the urge to even start this argument, youve got bigger issues than whether or not a text-mode library is as good as another

Zoids Quest project is a jump-and-run platform game.

Zoids Quest is a platform game in the style of old console games such as Super Mario World and Sonic the Hedgehog.

Players must help Zoid on his Quest by guiding him through many worlds containing tricks, traps, and monsters.

On the way Zoid can collect special magic runes which enhance his abilities and help defend against the many deadly foes.

This is the first public release.

Millers Quest! is a role-playing simulator game. It could also be described as a "fire-and-forget role-playing game". In other words, it is not a role-playing game in the most traditional sense, because there is absolutely no player interaction. The emphasis on this game is the simulation of role-playing.
So, it is a completely non-interactive computer role-playing game. "I guess its not fun then", I can hear you say. Wrong! Millers Quest! is, in fact, very much fun. It has all of the excitement of traditional MMORPGs with none of the effort to be put in mindless treadmilling.
You can watch your character grow more potent and more powerful, and you dont need to bore yourself with details like "okay, attack the monster, Im going to win anyway".
Millers Quest! was largely inspired by its direct ancestor, Progress Quest. It is written in Ruby programming language and as such it was largely also inspired by Dwemthys Array, without any of its clever metaprogramming stuff and general bore of having to use irb to play it.
Players of Progress Quest should be right at home with Millers Quest!. What tells MQ and PQ apart is the fact that MQ is not entirely progress-driven. In MQ, all monsters have actual stats. Theres actual, stats- and probability-based fighting involved.
Since dying in a continually running game is pretty damn boring, you get also revived and healed automatically if that occurs. MQ owes a lot of its continued existence to Ruby Development Tools, the Ruby environment for the Eclipse Platform.
Enhancements:
- The combat system wasnt working quite properly, and is now fixed (somewhat).
- A confusing display message has been fixed.
- New features include optional support for curses/terminfo, allowing better-looking and more comprehensive combat display by coloring the output. (This currently requires tput(1) from ncurses.)