Complete.Org: Mailing Lists: Archives: freeciv-dev: May 2005:
[Freeciv-Dev] (PR#13024) wanted: new script API types
Home

[Freeciv-Dev] (PR#13024) wanted: new script API types

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
Subject: [Freeciv-Dev] (PR#13024) wanted: new script API types
From: "Jason Short" <jdorje@xxxxxxxxxxxxxxxxxxxxx>
Date: Mon, 9 May 2005 23:38:17 -0700
Reply-to: bugs@xxxxxxxxxxx

<URL: http://bugs.freeciv.org/Ticket/Display.html?id=13024 >

Building type (struct impr_type, API_TYPE_BUILDING)

...for an improvement-built or improvement-started signal (needed for a
tutorial for wonders or first-building-built, for instance).

necessary fields: name, cost

Unit type (struct unittype, API_TYPE_UNITTYPE)

...for a unit-can't-be-built event (needed for a tutorial for settlers,
to give a hint as to why).

necessary fields: name, cost, attack power, defense power, HP, MP
desired fields: unit class name (this is hard)

Technology (struct tech, API_TYPE_TECH)

...for any tech-researched or tech-researching or tech-goal-set events
(obviously needed).

necessary fields: name

Government (struct government, API_TYPE_GOVERNMENT)

...for any government-available or government-changed events (needed for
a tutorial mode to tell a player to change governments).

necessary fields: name

Terrain (struct tile_type, API_TYPE_TERRAIN)

...simply for completeness, I think.  I'm sure it'll come in handy,
maybe for a tile-changed event signal.

necessary fields: name

All of these will be needed I think.  There are probably others that
escape me for the moment.  The most important field of each is the name
(which should be the untranslated name, as always).  Any other simple
fields should be included as well.  I think the index/id should be
hidden however (this will only confuse the script writer, as the API
interface should take care of all such transformations).

-jason





[Prev in Thread] Current Thread [Next in Thread]