Argila RPI Engine Down Loads
Current Version
Requirements and Warnings
Coders trying to run Argila will need to be familiar with tools such as gdb, gcc, lint, as well as be familair with the commands to manage directories, file permissions, passwords and server variables. You will need to be familar with Mysql, and be able to edit text files and the database structures and information. You may also need to do all of this on remote machines, so you will need to use tools such as telnet, ftp, sftp, and ssh. If any of this is unclear to you now, it will get much worse when you try to work with Argila. This is not a plug-and-play game. It is code, and it is generic. You will need to add a lot to it, to make it your own game, since each and every installtion of Argila and the game it supports are different. With that said, it does give the game coder a big headstart over a codebase written from scratch.
ARGILA 2.0
Argila 2.0 has arrived. Along with many small fixes to the main code, the most important feature is the addition of Lua. A TIMER triggers is coded in for rooms, mob and objects. All you need to do is come up with creative ways to use it. A few sample scripts are included in the full package. Addition of the triggers merely means finding the right location to call the triggers, and then deciding what you want to happen. Tha basic code for the Lua actions will be parallel to the code for the existing TIMER trigers.
Warning: As the Lua is embedded, there may be some difficulties with the installation of the Lua package. Rest assured, it is possible and merely needs the correct file linking for your make files. As this is dependant on each individual server, I am not providing complete instructions. It does work, trust me. For your convinance, here is a link for Lua 5.1 on it's own.
Older Versions
Argila 1-03 fixes many small issues and makes the inital set up easier. The makefile has been greatly simplified, and with the conversion of C++ double-slash comments to C style /* */, the code now compiles cleanly with -ansi flag. Addtionally, the makefile default set-up is now LINUX, with MacOSX changes indicated in the comment sections. This patch also inlcudes the wear_location fix.
Patches
The Argila 1-03 Update patch will update Argila 1-02 to the version 1-03.
As always, It is recommended that the changes be applied to the Test Port, and any issues with your code be resolved prior to moving the code to the Builder and Player Ports.
Patches under review
The following patches are under review and may not function. Use at your own risk. Feel free to download them and test them out. Discussion on these patches can be found at Patchs/Mods.
Version 1-02 contains fixes to the memory management system, as well as a fix for the registry-combat problem. A few changes to the code in nanny.c was made to move redundant code to a separate function. Additionally, the skill listing has been altered to make changing skills easier. A single struct now holds the information from the three structures, making changes less prone to error. A small enhancement was also added to the show v command for Rates, to make the display a little easier to read.
With the fix to the registry, combat is now possible. Also, you can enter multi-line descriptions for rooms, objects and any other use of the in-game editor. Notes can be made to any player now, just as if they were a bulletin board. The Guest login option from the first menu screen has been removed as it posed a security problem.
Caution: If you have built mobiles under previous versions of Argila, you may find some skills have been re-arranged. I tired to keep the changes to the worldfiles minimal, but Psionics were removed, and that may have an influence on any mobiles already created.
Older Patches
- patch1-02-1 (newly init mobs)
- patch1-02-2(small fixes/Linux)
- patch1-02-3(small fixes/MacOSX)
- patch1-02-4(getopt)
- patch1-02-5(socklen_t)
- patch1-02-6(ansi comments)
- patch1-02-7(makefile/linux)
- patch1-02-8(makefile/MacOSX)
The Registry Patch will patch the registry from Argila1-01 to solve the combat problem. Since it is such a small item, users may wish to use the diff listing to see which lines need to be deleted.
The bulk of the changes are dealt with in the Source Code Patch. This patch covers only the src directory. It is recommended that the changes be applied to the Test Port, and any issues with your own code be resolved prior to moving the code to the Builder and Player Ports.