System Planning - Weather & Time

[taladan]

Weather & Time

Calendar/Time

Automating the configuration of the Calendar & Time system is going to be the best way to avoid some of the hassle in configuring weather & time. The following is a tentative list of questions that should probably be touched on to set up the initial calendar.

Setup questions:

• What is your Calendar's root year? (0 A.D, The year of the Burning Mountain (23,357 CY) - This should be the starting point that we measure from. Year 1 is default)
• What is your year designator? (ex: BC/AD, CY, AG, %$, whatever)
• Epoch Designators (Age of stone, age of might, Days no longer spoken of, etc.)
• Season names (Influence Weather - Weather should inherit from calendar)
• Number of months in season (default 3)
• Time ratio (default 1:1)
• Number of months in year (default 12)
• Month names
• Calendar Start Month
• Calendar End Month
• Number of Days in each month (default 30)
• Day names
• Number of Days in year == total days in each month # Not settable
• Number of hours in a day (default to 24)
• Hour names (ex: Catholic Canonical Hours, Muslim Salah times, Jewish Hours, etc.) - Should be optional, also settable to a time range or possibly variable time range (as in Jewish hours)
• Number of seasons (default 4)

Weather

System needs to be able to trigger objects as well as rooms, test for is_room(), Weather can be a room Parent, store child objects (Glowing Orb, Weather Stone, Map on a wall) so that the weather can be indicated or described in some manner.

Exposed methods:

• is_rainy()
• is_windy()
• is_sunny()
• is_cold()
• is_foggy()
• is_hot()
• is_warm()
• is_cool()
• current_season() ¹
• current_year() ¹
• current_month() ¹
• current_day() ¹
• current_hour() ¹

¹ - These should be inherited from calendar/time