Glorious Alpha Two Testers!

Phase I of Alpha Two testing will occur on weekends. Each weekend is scheduled to start on Fridays at 10 AM PT and end on Sundays at 10 PM PT. Find out more here.

Check out Alpha Two Announcements here to see the latest Alpha Two news and update notes.

Our quickest Alpha Two updates are in Discord. Testers with Alpha Two access can chat in Alpha Two channels by connecting your Discord and Intrepid accounts here.

Siege Timer Suggestion

ArchivedUserArchivedUser Guest
edited June 2017 in Ashes of Creation Systems and Mechanics
The reason this timer was created was so a node can not be sieged consistantly until they lose and gives a city down time.  Intrepid stated that sieges have a set timer (3/4 weeks, not permenently set) that a node can be attacked which is reflected by the stage of developement of the defending node.  Intrepid has not dived into what can start a seige.  Most believe it would be the leadership of a local node making that decision.  "Hey guys, they have that one resource... and they have attacked our caravans before... their timer is almost down, lets siege them.- This timer seems like a lazy mechanic.  I would suggest a moba or RTS style initiation to sieges.  Nodes could send out troops based on resources spent.  There would still be the need to gain resources for seige equipment, food for troops, equipment for soldiers to travel towards a node but the travel time would give potential for more mechanics in the world.  Seing a group of NPC soldiers from a particular node pass could create powerful immersion to players and contribute to meaningful conflict.  That travel time could act as the 3/4 week period the team is looking for a siege initiation. This time could also be influenced by the NPC interactions on the road by either quests or conflicts by friend or foe.

Sending out a large resource that has meaningful travel time could open up the risks to an attacking force's home.


Sign In or Register to comment.