primem0ver
Emperor
Yup... its finally here. And not a moment too soon! This is an expansion that allows events for warlords and maybe in the future vanilla. I have some comments below about how Beyond the Sword will affect this mod but, first with a description:
CONTENTS OF THIS POST:
Here are the sections of this post in case you are looking for something specific:
Introduction to Events
Event ages
Modding
New Features for game play
New Features for modding
Known issues
Downloads (AT THE BOTTOM!)
Events: An Introduction
Events are a new concept to Civilization 4 and are introduced by this “expansion” mod (which was concieved of for the Genetic Era Mod back in October or November, long before the BtS announcement). Events can be both positive and negative. They can affect many things but most specifically they can affect units, population, buildings, cities in general, improvements, and the terrain (both features and terrain). Some events are completely random. Some events (natural events) may happen every turn but do not usually affect you. Other events depend on things like city health, unit location, and other non-random situations that can lead to events. Specifics for all included “vanilla*” events are included in this documentation. Finally, certain units can cause events. An example is the Great Prophet. In the Events engine expansion, a prophet can cause a “great plague” in an enemy city.
*IMPORTANT NOTE: Events are completely moddable like everything else in this game so they may vary if the mod you have downloaded has created custom or altered events. This documentation is for the standard “vanilla” version of the mod.
Event Ages
Another new concept that comes with this expansion are event ages. Ages are similar to Eras. One might even wonder why they were added except that Eras depend on a players position in the technology tree and Ages do not. Ages depend on game year and so they affect all players at the same time. The main purpose of ages is to allow for variations in the number of events that happen during certain time periods in the game. For example, one age is titled the “dark ages” and during this time you will experience a heightened period of plagues. See below for more information about this important time in history. Other ages also exist in the game. See the charts at the end of this document for more information.
Modding: (more specifics below... this is just an overview)
Events are completely XML defined and may be changed, added to, or removed by any modder who can alter XML files and knows how to make XML mod changes to the game (though it helps to be able to create buttons as well!). I STRONGLY RECOMMEND however that before you alter these files, you read the Modders Guide so that you know how events (and related infos) are defined.
I have included both a players guide and a modders guide with this “expansion” that help with the following:
The Players guide: is an “instruction manual” addition that should be included with any mod that uses this expansion and explains how to play the game with random events (important playing information and tips).
The Modders guide: is a handbook on how to use the new XML files, Python access, and SDK classes to enhance your own mods. There is also a technical reference to accompany this that includes technical details that may help SDK modders to understand how the Event Engine works.
A “standard” set of events has been shipped with this mod that I will call the “default” or “vanilla” events. Events and the concepts they rely on are defined in a new “Events” XML folder with 5 new XML info files (+1 new XML schema).
The new files are:
Events\CIV4EventClassInfos.xml
Events\CIV4EventAgeInfos.xml
Events\CIV4EventEffectInfos.xml
Events\CIV4EventInfos.xml
Events\CIV4EventTriggerInfos.xml
Events\CIV4EventEngineInfos.xml (basically an ini file for the engine)
(And the new schema file: Events\CIV3EventInfoSchema.xml)
Changes to game and game play:
New approaches and changes to modding:
Known Issues
Downloads
Currently the Acrobat version of the help files are not available. To read the events list, you will need MS Word. [WILL FIX SOON!]
The EventsForWarlords download contains the playable mod for warlords, the changed (and added) SDK files, and all the current documentation. If you use the SDK files in this download, there is some important information regarding SDK merging in the Modders Guide. (There are some pre-processor defines you must add).
The Full EventsForWarlords SDK download contains the entire SDK with all things needed for events added to the project and solution files.
CONTENTS OF THIS POST:
Here are the sections of this post in case you are looking for something specific:
Introduction to Events
Event ages
Modding
New Features for game play
New Features for modding
Known issues
Downloads (AT THE BOTTOM!)
Events: An Introduction
Events are a new concept to Civilization 4 and are introduced by this “expansion” mod (which was concieved of for the Genetic Era Mod back in October or November, long before the BtS announcement). Events can be both positive and negative. They can affect many things but most specifically they can affect units, population, buildings, cities in general, improvements, and the terrain (both features and terrain). Some events are completely random. Some events (natural events) may happen every turn but do not usually affect you. Other events depend on things like city health, unit location, and other non-random situations that can lead to events. Specifics for all included “vanilla*” events are included in this documentation. Finally, certain units can cause events. An example is the Great Prophet. In the Events engine expansion, a prophet can cause a “great plague” in an enemy city.
*IMPORTANT NOTE: Events are completely moddable like everything else in this game so they may vary if the mod you have downloaded has created custom or altered events. This documentation is for the standard “vanilla” version of the mod.
Event Ages
Another new concept that comes with this expansion are event ages. Ages are similar to Eras. One might even wonder why they were added except that Eras depend on a players position in the technology tree and Ages do not. Ages depend on game year and so they affect all players at the same time. The main purpose of ages is to allow for variations in the number of events that happen during certain time periods in the game. For example, one age is titled the “dark ages” and during this time you will experience a heightened period of plagues. See below for more information about this important time in history. Other ages also exist in the game. See the charts at the end of this document for more information.
Modding: (more specifics below... this is just an overview)
Events are completely XML defined and may be changed, added to, or removed by any modder who can alter XML files and knows how to make XML mod changes to the game (though it helps to be able to create buttons as well!). I STRONGLY RECOMMEND however that before you alter these files, you read the Modders Guide so that you know how events (and related infos) are defined.
I have included both a players guide and a modders guide with this “expansion” that help with the following:
The Players guide: is an “instruction manual” addition that should be included with any mod that uses this expansion and explains how to play the game with random events (important playing information and tips).
The Modders guide: is a handbook on how to use the new XML files, Python access, and SDK classes to enhance your own mods. There is also a technical reference to accompany this that includes technical details that may help SDK modders to understand how the Event Engine works.
A “standard” set of events has been shipped with this mod that I will call the “default” or “vanilla” events. Events and the concepts they rely on are defined in a new “Events” XML folder with 5 new XML info files (+1 new XML schema).
The new files are:
Events\CIV4EventClassInfos.xml
Events\CIV4EventAgeInfos.xml
Events\CIV4EventEffectInfos.xml
Events\CIV4EventInfos.xml
Events\CIV4EventTriggerInfos.xml
Events\CIV4EventEngineInfos.xml (basically an ini file for the engine)
(And the new schema file: Events\CIV3EventInfoSchema.xml)
Changes to game and game play:
- New MAIN Concept: Events. There are four types of events that can occur: natural, conditional (often environmental), random, and “triggered” (caused by special units).
- Natural events can occur anywhere on the map and most have an “intensity” associated with them such as the Richter scale for earthquakes. They don’t necessarily affect players unless a player is near where they happen. Just like in real nature, less intense natural events happen more frequently than more intense ones (though the actual time off occurrence varies unpredictably). You may not even experience the BIG one at all…but then again… you just might!
- Cities and Units can be affected by their location and circumstances such as terrain, by environment, by things such as the cold, and the lack of water in the desert. Cities can suffer from disease if their health gets too low (conditional events).
- Random events such as drought, a wealthy landlord joining your empire, an extra great person, and “good” harvests can occur at any time.
- Some events cause effects that last for multiple turns: such as the “revel” or “world fair” raising your happiness or culture rate, or any number of seven different factors (i.e. happiness, health, food, production, gold, research, and culture). Some bad events can have effects that last multiple turns as well. For example, a plague will cause unhealthiness and unhappiness in your city for a few turns.
- There is a new type of “special” unit: the Events unit. Events units (such as the jester) can cause positive events in your cities that raise happiness, health, commerce, and possibly other things as they go around lifiting your kingdoms spirits. Each great person unit can also cause their own event, some good, some bad (such as the prophet plague!).
- There is a new Great Unit (Which still needs some work): Great Explorers Details about this unit will wait for another post.
- New MAIN concept: Event ages. Event ages are period of increased (or decreased) events. Beware of some of them and make sure you are prepared with event units when certain ones come: they will spread suffering across the land unless you have event units prepared to help with your kingdoms morale! Beware especially of the Bubonic plague during the dark ages!
- Exploration and cirvumnavigation are affected by events! Because your units can now die of exposure (frostbite), heat exhaustion (in deserts), and simply getting lost at sea (stuck in the doldrums zone), so you must be careful when exploring, particularly the sea in the early game.
- Certain techs are key to exploration. The compass and astronomy are vital to not getting lost at sea.
- There are new uses for several bonuses (also called resources). For example: sheep, cotton, and/or especially fur will be a significant advantage in the early game because they reduce your chances for frostbite. Frostbite can keep you from circumnavigating the globe without this bit of help. (NOTE: uses are not currently reported in bonus help)
- There are new kinds of special buildings and improvements. Weather stations (building) and seismic stations (improvement not yet implemented but possible) can be built to minimize effects of earthquakes, hurricanes, and other natural disasters.
- The Interface is event friendly, telling you when events occur, the chance an event will occur when moving into a new spot, telling you what events are affecting your cities well being (in the city screen). This still needs to be improved some.
- You can automate special events units. By automating event units, they will go around looking at where they can improve your empire’s well being by hosting events. They will also consider helping and hurting your enemies so be careful!
- New way to attack opponents. You may unleash the fury of prophets and other units capable of triggering “bad” events on your opponents cities. Watch out, because they can do the same! You can also use this to get them to go to war with you!
- New approach to appeasing an enemy: You may now do missions of peace by causing good events in enemy cities. Even when you are at war! But be VERY careful, your event units can be attacked. [MUST IMPROVE AI FOR THIS]
New approaches and changes to modding:
- ALL ASPECTS OF EVENTS, EVENT AGES, and EVENT EFFECTS that have been defined by the original version of this mod ARE MODDABLE THROUGH XML. See the modders guide for more information.
- All event XML is located in a new XML folder: Events.
- You can add (or remove) events (and anything having to do with events such as event ages) in your own mod.
- Each event can have its own sound and icon added. There is a default that is used if one is not defined [NEED TO ADD THE DEFAULT ICON]. If you add your own, you must be able to add your own sounds and sound scripts to the XML.
- There is a separate folder for each of these new sets of sounds and icons.
- Events help streamline missions: because “anything” can be considered an event and many “mod” missions do what events now do, and particularly because the event engine provides an interface for custom events affects, new missions can now be added without much SDK development. For regular “event” missions with effects already defined in the standard event XML, adding new missions is as simple as adding the appropriate XML and a new mission enum to specially marked places in the events version of the SDK.
- For special case missions where the effects are not in the standard event XML the procedure is the same as above except that you must also add an EVENTEFFECT_ enum to both the eventinfo in XML and to the event effect handler in the SDK. Then all you must do is add your special EVENTEFFECT_ procedure (either in the handler itself or in your own custom procedure). (More details in the Modders guide).
- EVENT MISSIONS: IMPORTANT NOTE: if you are adding your own event missions, one thing must be considered: Any unit that has an excessive amount of event missions (say more that 3) will cause a significant amount of AI time per turn, particularly if the missions are different in their nature. The reason is because the AI must decide on three things when picking the next mission: 1. What kind of event will we do? (ie. Help our own team, hurt a team, try peacemaking with a team?) 2. Who should I attack/help (if not helping self)? 3. Which of my missions is the best for what I want to do? The best plot (city) for the mission is already decided for him once he has decided which mission to try, but he will still cycle through all missions if he does not find a best plot for each mission he tries in turn. The best way to avoid this is to have the unit only perform one kind of mission. In other words… have a war unit only do war missions (not self help or peace). The same goes for the other options.
- Their is a full Events SDK that you may download for your use
Known Issues
- There is a crash that occurs when the Great Explorer dies. **FIXED!**
- For some reason, many windows Vista users have had difficulty getting this mod to load. It crashes during XML load. SDK USERS WITH VISTA: I COULD USE SOME HELP WITH THIS... please let me know if you can help because I do not currently have vista.
- There is one situation where event text is not working properly (when the event is reported to the human player).
- Hurricanes are either too many or too few. There is a bug with getting the right balance because of the way they are generated. Right now there are too few.
Downloads
Currently the Acrobat version of the help files are not available. To read the events list, you will need MS Word. [WILL FIX SOON!]
The EventsForWarlords download contains the playable mod for warlords, the changed (and added) SDK files, and all the current documentation. If you use the SDK files in this download, there is some important information regarding SDK merging in the Modders Guide. (There are some pre-processor defines you must add).
The Full EventsForWarlords SDK download contains the entire SDK with all things needed for events added to the project and solution files.