Iberia

Introduction

After the end of the Punic Wars in the third century BC, Rome focused all its strength on conquering the Iberian Peninsula. Initially, the invasion was successful and Rome conquered most of the peninsula with relative ease.

Led by Consul Servius Sulpicius Galba, Roman troops proceeded to eliminate the last remnants of the Lusitanian resistance. Fearing the destruction of their lands, the Lusitanians sent an emissary to Consul Galba requesting an armistice. Galba obliged, suspending the Roman offensive and promising to leave the remainder of the peninsula to the Lusitanians.

As it turned out, Galba had lied. When the Lusitanians attempted to claim the lands they were promised, Galba's army was waiting for them. The unarmed Lusitanians were killed in massive numbers. A man named Viriathus was among the few who managed to escape the massacre.

After losing such a substantial amount of troops, Lusitanian military leaders were prepared to negotiate a new treaty with their enemies. Viriathus, however, hadn't forgotten Galba's treachery. Instead of a treaty, he suggested a counteroffensive. The Lusitanians supported this idea wholeheartedly.

Viriathus and the Lusitanian army were severely outmatched by the better-armed and better-organized Romans, so Viriathus executed guerilla tactics, orchestrating imaginative ambushes and clever flanks. Charging forward with iron spears, short swords, and resounding warcries, the Lusitanians left a trail of enemy armies in their wake, freeing the Iberian Peninsula from Roman control.

About Iberia

Iberia project started in 2000 just as a hobby, and in early stages was only meant to be played offline. With slow but constant developments suffered multiple revamps, and in 2006 got a dedicated server. Since then it is continuously online and free to play.

Features

• ANSI colour, MXP, MCCP, MSSP, MTTS/TTYPE and MSP support.
• All original code, extendable through Java or IME scripting even at run-time.
• Can connect to databases on flat files or database engines via JDBC/ODBC.
• MUD boards for public and private messaging. Based on privileges to players or group of players.
• Extendable naming for commands (can be set up for abbreviate command names or other syntax similar to other MUD engines), items and NPC.
• Simple security system, based on privileges to players.
• Solo and party quests, including automated, time-based and event-based triggering.
• All original combat system, focused on gladiatorial and "realistic" combat but always having playability in mind (multiple layers for armour protection, player can focus on body area to hit or to protect, player can define a combat style that influenciates damage made and turn duration).
• Thread based system.
• 7 ethnic groups to choose (the major ones at that time in the region).
• Leveless and classless (limited number of skills per character, and each skill upper limited based on character experience).
• Developed army combat system (players can command NPC armies in combats against other armies; considering the ratio of living soldiers of Roman and Barbarian armies, regions are then controlled by one of those sides).
• IC language system (each ethnic group has it's own main language. When speaking, other PC will only read sentences properly based on speaker and listener skill points).   
• Translation system (it let players set a language other than English to translate rooms, items and NPC descriptions, and also text in all communication lines - says, tells, OOC and I3\GV)
• Built-in map system, used via "map" command. It has ASCII art or descriptive outputs.
• No hungry, thirsty or tired by movement.
• Day (sun), night (moon), weather and season (summer/winter) systems, which can influentiate player actions (as combat or army combat).
• Builder authoring in each item/room/NPC created (checked via "author" command)
• Additional "today" description in each room that gives information about that room in the present day (geographical correspondence).
• Built-in alias system.
• Trigger system.
• Social emote system (around 400 emotes, which can be targeted or not).
• Activity system for set an activity to players perform when logged off.
• Surname system (setting a one time surname will give that player the ability to authorize or not others players to use the same surname).
• Player non-permanent death (skills and experience penalties for each "death").
• MUD help files and news board convertible in real-time in html pages.
• Intermud connection chat line, via Intermud-3 and Grapevine protocols.
• Built-in paginable text system: if huge amount of text must be sent to client and doesn't fit on client screen size, it stores exceeding text in a buffer that can be seen by user action (pressing enter shows next page).
• Easy online building system.
• Most commands are "syntax friendly", as they have aliases equal to other MU* engines command syntaxes (LP, MERC and others).
• Autocomplete system (using the character '?' followed by any character(s) will show you the commands that start by those characters).
• Name generator system, to help builders generate adequated/themed names in their creations.
• Description generator system for rooms, NPC and items, to aid builders a bit more. It's half way between a bare bones and finalized room/NPC/item.
• Thematic augur/seer/priest as a lifestyle.
• Items are saved in character between logins (one only looses them between on reboots).
• Gladiatorial combat and bet system (earn money by betting or fighting as a gladiator, though always risking your life).
• Connection through normal telnet port (5900), TLS\SSL port (5899) and WebSocket Secure port (5901 - our web client).