Siege Declaration Items

I think that items/resources that are used to declare a siege should either have an expiration date or some other way as to not allow players to hoard and stock pile them. This is important so that a group can't declare war back to back to back on all neighboring nodes or maybe even declare war on many nodes at the same time. I think it would make more sense if the attacker had to more intentionally prepare for each siege rather than mass farming and stock piling for future sieges. Would this inhibit the sandbox too much, or does it seem like a reasonable idea? What are your thoughts on this topic?

P.S. I am aware that a node receives a defensive cooldown which will not allow for it to be attacked again for a period of time after it was just attacked.

Find more posts tagged with

Comments

Varkun

Just speculation but one way to limit the siege declaration item is to simply put a timer on it. Yes you need all of these resources that you can stockpile but it takes days weeks or months to create the declaration item and once you have it then you can declare a siege. To stop people from stockpiling such items you can only have one such item stored at any one time. Once it is used you can then start the process again to create another one but again this could take days weeks or months. Remember this item/thing has to be created thus the time and we have no idea what type of highly skilled gathers/processors/crafters may also be needed in the process.

Another thought is perhaps while you are preparing the siege declaration item all other work in the node grinds to a halt as all effort goes to creating the item.

VmanGman

Varkun wrote: »

Just speculation but one way to limit the siege declaration item is to simply put a timer on it. Yes you need all of these resources that you can stockpile but it takes days weeks or months to create the declaration item and once you have it then you can declare a siege. To stop people from stockpiling such items you can only have one such item stored at any one time. Once it is used you can then start the process again to create another one but again this could take days weeks or months. Remember this item/thing has to be created thus the time and we have no idea what type of highly skilled gathers/processors/crafters may also be needed in the process.

Another thought is perhaps while you are preparing the siege declaration item all other work in the node grinds to a halt as all effort goes to creating the item.

That’s what I’m saying. I think there should be some kind of limitation on it and I was curious if others see the same issue.

Varkun

I know that is what you are saying just my thoughts on how to stop the problem you proposed from happening. I do agree it could be a problem but then having to fight multiple sieges throughout a zoi could make for interesting times.

Even with a timer placed on the building of declaration items what is to stop other settlements who are under a metropolis ZOI from being fed resources to create a siege declaration item on behalf of the metropolis and then go declare a siege on behalf of the metropolis and be backed up when the siege happens.

But then I think this is part of the idea with the whole political side of the game and the intrigue that would ensue.

Noaani

To be clear, I am still not saying a timer or some such on the actual quest item used to declare a siege wouldn't be a bad idea (I don't think it would be necessary, but that doesn't make it a bad idea).

What I am saying is that I don't see that item as being the barrier to a successful siege. To me, the declaration item is little more than a token that needs to be in the game so players need to put some effort in so that sieges are not just declared haphazardly. This is speculation, but it is the same level of speculation as anything else in this thread.

I'm also not saying that I think a node stockpiling resources for "A" siege would be noticed - but stockpiling for many would be. If absolutely nothing else - the other meteopolis' on the server would be asking themselves why the fifth one hasn't sieged anyone in months.

The other thing is that this whole idea of stockpiling essentially requires everyone to do it instead of attacking when they are able. Most metropolis' will siege another meteopolis every few months - and if you are deciding which metropolis to attack, the one that hasn't been sieged or declared a siege in months would likely be your target.

The game will also assist in this, apparantly, with rewards for successfully sieging a node going up the longer the node remains un-sieged.

As with most things in this game, we don't have enough information to know what will or will not happen, or to provide Intrepid with amy useful feedback.

You have your opinions on how the siege system will work, and you see issues with it. I have my own opinion of how it will work, and it doesn't have those same issues. I'm fairly sure neither of us are 100% right in how it will end up.

What we do know for sure is that Intrepid want sieges to happen, and want meteopolis' to fall. The game itself is based around this happening.

Since we also have a time limit on how often a meteopolis can be sieged (55 days), it is probably fair to say that Intrepid want metropolis' to be sieged about that often.

Since players are unable to siege a meteopolis more often than that, I still do don't see the issue.

Basically, we can't under any circumstance siege any node more often than Intrepid want us to be able to.

Ventharien

noaani wrote: »

What I am saying is that I don't see that item as being the barrier to a successful siege

Most metropolis' will siege another meteopolis every few months

I don't think the idea is that it will be THE barrier, but that it puts a hamper on problems that have arisen in other games with similar ideas (open world destructibility pvp.)

And i don't think that will be the case. From what we've heard sieging a metropolis is going to be a monumental task (Artfully described as being etched into the servers memory). Not only will it take a signifigant amount of time to become a metro, the limit on 5, and the current design choice of a successful siege annihilating the node completely, I see sieges being aimed in succession at vassals in order to put pressure on and hopefully delevel a metro before directly assaulting it. Otherwise every expense would be issued in it's defense, and your win chance would be much more narrow. At least, that's how it's seemed to me from the info we have, and kind of how i'd prefer it to be. More campaign than single move.

Noaani

Ventharien wrote: »

noaani wrote: »

What I am saying is that I don't see that item as being the barrier to a successful siege

Most metropolis' will siege another meteopolis every few months

I don't think the idea is that it will be THE barrier, but that it puts a hamper on problems that have arisen in other games with similar ideas (open world destructibility pvp.)

And i don't think that will be the case. From what we've heard sieging a metropolis is going to be a monumental task (Artfully described as being etched into the servers memory). Not only will it take a signifigant amount of time to become a metro, the limit on 5, and the current design choice of a successful siege annihilating the node completely, I see sieges being aimed in succession at vassals in order to put pressure on and hopefully delevel a metro before directly assaulting it. Otherwise every expense would be issued in it's defense, and your win chance would be much more narrow. At least, that's how it's seemed to me from the info we have, and kind of how i'd prefer it to be. More campaign than single move.

Successfully sieging a metropolis will be monumental.

Not all sieges will be successful.

I don't have any info at all on how attacking a vassal of a metropolis can directly delevel that metropolis.

It can delevel the vassal, and that in itself has value - but deleveling the meteopolis?

Gimlog

@noaani in theory if you destroy enough vassals of the metropolis, you could affect the amount of xp that maintains it at metropolis stage and it may drop if the citizen fail in filling the deficit.
This should be one of the best options to deleveling a metropolis when successfully siege it isn't a option.

For the flags who may be stacked, I definitely can't find a scenario where it could happened.
Content will be lock behind metropolis stage so by time the veterans of a server will seek this content and rise the 105 nodes at metropolis stage to experiment the contents of it. They may siege metropolis to rise a other be stacking won't be necessary for this goal.

Maybe I'm not imaginative enough...

Child Item