Jump to content

Search the Community

Showing results for tags 'triggers'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Welcome
    • Announcements / News
    • Introductions & Off-Topic Discussion
    • Help & Feedback
  • 0 A.D.
    • General Discussion
    • Gameplay Discussion
    • Game Development & Technical Discussion
    • Art Development
    • Game Modification
    • Project Governance
    • Testing

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests


First Name


Last Name


Skype ID

Found 4 results

  1. Sander’s suggestion of me making maps and letting the 0 AD forummers take charge of the triggers made me think deeply of how best to present a scenario that will cover every possible trigger that I usually use in designing scenarios and campaigns. Disclaimer: All of the trigger suggestions I present in this post can be done and implemented with the editor of Empire Earth, of which I have been “schooled”. In no way am I saying that EE is better than 0 AD. No, dear sirs. I'm attempting to at least make Atlas a tool that I can understand and use, without being a programmer myself, dim-witted that I am. I hope I made that very clear. The campaign I’m about to describe takes part on the later years of Alexander’s life – the Battle of Hydaspes River, the fateful way home, his death and the rise of the Successors. Like my EE scenarios, it will take place into a fairly large map, to ensure the effects of player choices and the continuity of the branching storyline. INTRODUCTION After a short cinematic about Alexander and details of the events leading to the Battle of Hydaspes River, the Human player is given the option to choose between being an Infantry commander or a Cavalry commander. In 0 AD, I can see this as being done by forcing the player to choose between creating Cavalry or creating Infantry from the town center. If the player chooses to create an Infantry Type, the life stories of all of Alexander's famous Infantry commanders will be unlocked. If the player chooses to create a Cavalry Type, the paths of the cavalry commanders will be yours to relive. Once the choice is made (triggered to fire if the Player owns 1 unit), the Town Center becomes owned by the allied AI, and the only unit the player controls at this point is the first unit he created. (Creating a female villager unlocks the infantry stories). This initial unit would then act as the “scout” unit sent by Alexander, most probably for an errand prior to the battle. The player is then instructed to have this unit go back to Alexander and his army. Once this unit meets up with Alexander, PART 1 begins. Part 1: River of Blood Alexander’s army is controlled by an allied AI, the Indian army is controlled by the enemy AI. Each block of AI (or each major group) has an officer that lead’s that group. This means the AI needs to be passive for both armies to be seen in their historical battle formations. Once the “scout” unit meets up with Alexander, the Human player gets to control either the infantry or the cavalry of Alexander’s army (depending on the previous choice). This put specific groups of existing units under the player’s ownership. Once the the condition “Player owns more than 2 units” fire, AIs become active and the Battle of Hydaspes River is played out. (A more complex one is the ability to control how the AI’s army move in the battlefield – for example, the enemy right wing going from right to left, or the enemy archers specifically attacking Alexander, or any other trigger effect that controls each unit or group under the AI). During the battle, specific gameplay features will be present: 1. Paid to Kill trigger – for every enemy unit the Human player kills, a random resource is given to him. 2. Veterancy – a unit with more kills get more experience 3. Morale – if an officer (either enemy or allied) is killed, a group previously tied up to that officer routs. 4. Ammunition and supply –units may from time to time lose their ability to attack and needs to come back to the rear to get more “ammunition” and supply and then go back to the battle afterwards. 5. Battle Points – the number of enemy units your units killed plus the number of veterans you owned minus the number of units you lost The goal of the battle is not to completely annihilate the Indian army, but either or all of the conditions can be met to have the battle stopped and be victorious: 1. Wounded King Porus 2. All Indian cavalry is killed 3. All elephants and archers killed After a short cinematic declaring the surrender of Porus, the remaining Indian army is integrated to Alexander’s army. The 2nd part begins. Part 2: At World’s End After the cinematic, a few citizens are spawned near the battlefield. It would be cool to have the citizens “gather” resources from fallen soldiers. After citizens are spawned, all your army and those of Alexander’s become owned by the allied AI. The player is then instructed to create at least 2 town centers and/ or reach the town phase. Here, Alexander’s army becomes sort of a garrison of the town, while you create your own army (not exceeding 75 units – for the moment to avoid lag). While gathering your own army, you get an optional quest of conquering the Indian town of Sangala. Alexander’s army is tired (and mutinous!). They will not help you. Sangala is moderately defended (with spawning enemy units inside the town, in intervals until the town center is destroyed). Once Sangala is taken, the player is then presented with 2 choices: if you have unlocked the infantry side, Alexander and your men are forced to make your way back home. No questions asked. If you have unlocked the cavalry side, you get to at least try to reason with Alexander (this represents Coenus’ – a cavalry commander who is the hero of the Battle of Hydaspes - role in convincing Alexander to turn back). At this point, if Alexander’s army Battle Points is more than your own Battle Points, you can go and continue EASTWARD wherein you get to TRY and conquer the Indian subcontinent and the other empires present there. Part 3: To The West (If you unlocked the cavalry side and decided to go Eastward, this would not apply). After the elapsing of say, 30 game minutes (for infantry side), or after conquering the Indian town and deciding to go back home (for cavalry side), the player's units become the allied AIs again. The player would, however, still control villagers. An instruction to build ship transports would become the next objective. After say 5 ships, Alexander and his men becomes yours to command again, but the rest of the AI within your surroundings become allied too, so you can't attack them. Your objective is to transport the army southwards and reach the Indian Ocean. Once you reach the population cap of around 150, all your buildings will be turned to allied and your villagers/ citizens will not be able to create buildings anymore. The journey back home begins. The journey south will not be an easy task. While you now control both Alexander's army and your own army, you have hostile native tribes to contend to. The player loses the game if his population drops to a certain level. Decision-trees will also be present: For the infantry side - after successfully taking the capital city of the Mallians, you can decide to make this area your base of operations. You will be asked to choose. If you choose, Alexander will take control of your existing army, and in turn, you will own all undamaged buildings and remaining Mallian units in the area + some of the mercenaries and Thracian units. Peithon, a phalanx battalion leader, together with Thracians were tasked and chose to live in this area historically. If you decide to do this, you'll relive this commander's later exploits. For the cavalry side (or if you just choose not to remain in Malian territory) - you continue to go on, and conquer 2 to 3 more Indian towns. One, heavily fortified and a capital, opens its gate to you if you have superior numbers compared to that AIs garrison. If not, you need to capture it. You then need to create a presence (most probably build a fortress in the southern-most city). Once you create that, all of your units become Alexander's again. The next rebellion will be specifically for the infantry side. (The infantry side) After a certain number of game minutes, you'll be given instructions to pacify the rebellion near your area. Alexander's army at this point is just allied with your enemies. Can we task units off-map (meaning they become invisible) and inaccessible, making them re-appear directly near the Indian Ocean afterwards? Still on the infantry side, you need to conquer/ destroy all the enemy towns in the in the Indus Valley. After having destroyed or subdued the enemy towns, Part 4 will begin. (The cavalry side) The decision is now to split the army into 3: - 1 to be commanded by Alexander himself and will go to the Gedrosian desert - 2 to be commanded by Craterus, which will go to the Mountains - 3 to be commanded by Nearchus, which will build a naval base and refit the ships. The player will choose either of the three, through either selecting units, or simple "Chat" triggered conditions. Part 4 will then begin. ...Shall be continued. More cool parts in my head to come, just no time to type...
  2. Not finished. Missing: Triggers.Details. First update: Second update: Now playable in game. Constantinople_Midnigth_Assault.zip
  3. Hi everyone! We decided it would be a good idea to do some pioneering work on trigger-based scenarios. Hence we are going to create a trigger-based scenario called Athens Triumphant. The main purpose of this project is logically to do pioneering work on triggers, to provide a base for other maps and to get our Scenario Designers accustomed with the Trigger functionality in 0 A.D. This scenario deals with the Greco-Persian Wars. We divided it roughly into three parts: Battle of Marathon, Defense of Athens and the Battle of Salamis. We created a story diagram to give an easily readable overview of the story line. Note that this could be changed in the future. We have used the Athens Sandbox as a base to build our map upon. Here is the current status (with some triggerpoints and names placed): We'll keep you up-to-date with weekly updates! Keep in touch!
  4. You probably already had seen me releasing this map in the Athens Triumphant a couple of weeks ago. It turned out to be the ultimate trigger sandbox for me so I continued its development and today it is finished! I hereby proudly present the first ever(!) storyline-driven scenario for 0 A.D.: A Silent Day In Gaul I don't want to spoil all the fun by giving a full overview of the map so I'll stick to sightseeing some of the nature that you can see in this map. Read this if you're having trouble with the scenario. SPOILER ALERT!!! Compatible with Alpha 18? Yes, it is! Just download the appropriate version. Changelog:v1.6: - Strengthen the bandit camp to prevent (too) early rushes. - Adapt to A18 balance changes. - Add some additional information for the player. - fix crash on SVN. (separate version for A18) v1.5: - implement Shieldwolf's suggestion about the more challenging endgame - update the visibility flag to svn's latest changes v1.4: - Remove a debug warning v1.3: - decreased the difficulty further by shortening the waiting time and giving additional resources v1.2: - Decreased the difficulty (I found it pretty hard even on easy difficulty) - Added details to the road - Repainted the river - Added support for repeating objectives v1.1: - Added player names - Fixed a warning v1.0: - Initial release map_A_Silent_Day_In_Gaulv1.6 - Alpha 18.zip map_A_Silent_Day_In_Gaulv1.6.zip
×
×
  • Create New...