Ideas for Stendhal/Magic

• Play
  • Manual
  • Beginner's Guide
  • FAQ
  • Ask for Help
  • Events
  • Videos
  • Rules
  • Groups
• World
  • Atlas
  • Dungeons
  • NPCs
  • Levels
  • Creatures
  • Items
  • Quests
  • Games
  • History
  • Achievements
  • Houses
• GMs
  • Administration
  • How to be a GM
  • Scripts
  • Guide for admin
• Contribute
  • Chat
  • Bugs
  • Testing
  • Graphics
  • Sound
  • Item Ideas
  • Atlas
  • Creature Ideas
  • Quest Ideas
  • NPC Ideas
  • Events Ideas
  • Achievement Ideas
  • Open Tasks
• |
• Extend
  • How to add items
  • How to add Creatures
  • How to add quests
  • How to add NPCs
  • How to create maps
• Develop
  • CVS (Source Code)
  • Bugs
  • Meetings
  • Testing
  • Code Design
  • Jenkins
  • Ideas
  • Open Tasks
  • Patches
  • API Reference

• Build & Host
  • Building
  • IDEs
  • Hosting
• |
• Misc.
  • Third Party Projects

Ideas for Stendhal

• RP Proposal with Skills
• RP Refactoring
• Character Classes
• Items
• Magic
• Effects
• Pets and sheep
• Alchemy and Crafting
• Upgrading weapons
• Temp. stats increase
• Containers
• Item Deterioration
• Player vs. Player Challenges

Mostly implemented

• Player to player trade
• Auction system
• Player parties
• Implementing Poison in combat
• Pushable Blocks

Related pages

• Ideas for Stendhal
• Quest Ideas
• Achievement Ideas
• StendhalEconomy
• StendhalRefactoringMiscRP
• StendhalRefactoringRaids

Previous discussions from meetings

• Arianne Project Meeting 2010/Development Discussions

Design idea

• Spells should be configurable via XML
  • works so far see light.xml for example in CVS
• Spells should follow the natures defined via the former DamageType
• Spells have limitations
  • limited casting frequency (cool down time)
  • wearing special equipment (example in code)
  • spells should need knowledge to learn for casting them (partly )
• Spells are separated into 2 parts:
  • The spell itself defining nature, mana use, cool down time and other possible prerequisites like equipment
  • Spell's effect defining what the spell does i.e. a simple healing spell just uses a healing effect that could be reused for a mass healing spell affecting all players in range
• Spells use mana
  • necessary attributes called mana and base_mana are already there
• Mana should be regenerated
  • via potions
  • slowly when no attacks are aiming at the player
• Client Integration
  • Client server communication
  • Small images to represent a spell
  • GUI integration
    • Show spells
    • Cast spells
  • Allow early testing
    • Script SummonSpell to obtain a spell
    • Slash action to cast a spell /cast
    • Mana can be manipulated via /alter (was already there)

Spell Ideas

• Light
  • Heal - Healing yourself or multiple players around
  • Shield of Light - Increase defense for some time
• Dark
  • Drain - Draining health from the enemy to heal yourself
• Ice
  • Freeze - Slow down an enemy for some time
  • Snow Storm - Push away enemies
• Fire
  • Fire ball - Ranged attack on one enemy
  • Explosion - Ranged attack on several enemies + pushing away the enemies around ( + damaging yourself a bit)

Open Issues

• Learning Spells
• Necessary Equipment
• Graphics for Spells? Spellbooks?
• Client integration?

TODO

• effects should be configured in XML instead of subclassing Spell
• instead of subclasses of spell defining separate preconditions for a spell the effects should do that