view api/Requirements/AbstractUnitRequirement.cs @ 165:71e50c0884a2

Fixes #194: Make unit equipment optional * Make unitEquipment tag optional (old schema could get us in to a situation where the race didn't define equipment but the unit had to reference something!)
author IBBoard <dev@ibboard.co.uk>
date Tue, 06 Oct 2009 10:37:08 +0000
parents 2f3cafb69799
children
line wrap: on
line source

// This file (AbstractUnitRequirement.cs) is a part of the IBBoard.WarFoundry.API project and is copyright 2008, 2009 IBBoard.
//
// The file and the library/program it is in are licensed and distributed, without warranty, under the GNU Affero GPL license, either version 3 of the License or (at your option) any later version. Please see COPYING for more information and the full license.

using System;
using IBBoard.WarFoundry.API.Objects;

namespace IBBoard.WarFoundry.API.Requirements
{
	/// <summary>
	/// Base abstract class for all requirements related to adding/removing something from a Unit (e.g. adding equipment or abilities)
	/// </summary>
	public abstract class AbstractUnitRequirement : AbstractRequirement
	{		
		protected abstract AbstractFailedRequirement CanAddToUnit(Unit unit);
		protected abstract AbstractFailedRequirement CanRemoveFromUnit(Unit unit);
		
		public override AbstractFailedRequirement CanAddToWarFoundryObject (WarFoundryObject obj)
		{
			AbstractFailedRequirement fail = null;
			
			if (obj is Unit)
			{
				fail = CanAddToUnit((Unit)obj);
			}
			else
			{
				fail = new FailedRequirement(this);
			}
			
			return fail;
		}
		
		public override AbstractFailedRequirement CanRemoveFromWarFoundryObject (WarFoundryObject obj)
		{
			AbstractFailedRequirement fail = null;
			
			if (obj is Unit)
			{
				fail = CanRemoveFromUnit((Unit)obj);
			}
			else
			{
				fail = new FailedRequirement(this);
			}
			
			return fail;
		}
	}
}