v2.5 tweak ideas - discussion thread
Moderators: Staff, Game Staff
- Kaz
- Administrator
- Posts: 2614
- Joined: Thu Sep 24, 2009 1:27 am
- Location: The Vinyards of Fernabergia
- Tempers Ball Posts: 3873
- Tempers Ball/Braggarts Hall Alt: Kaz
- Contact:
v2.5 tweak ideas - discussion thread
This thread is not really a 'guilds-only' thread, I'm just posting here as it's the forum with the most activity.
It's that time of the age when I'm starting to think about how things have gone, comments I've read, ideas that have been suggested.
There are three suggestions that I'd like to discuss.
1. Turn the downhit prevention code back on, that prevents kingdom declarations for downhits.
[edit] Feel free to continue to discuss this option, but it would seem that most players thus far, would like to see the code remain off in all games other than bloodbath
2. Configure a maximum size for a Restore, to prevent huge kingdoms just restoring back again after being broken.
[edit] We are still actively discussing this, several interesting ideas have been made for how to tweak this system
3. Add a time-based period of protection to the beginning of the age, a bit like you had at the start of LMS/LQS/LGS
[edit] Feel free to continue to discuss this option, but it would seem that most players thus far, do not feel that this is an option that should be pursued at this time
TWO ADDITIONAL QUESTIONS
4. Should you be unable to restore for 24 hours after sending a cash caravan?
5. Should Restore take away most of your Elan? i.e leave you with 500 elan?
note: 300 Elan = `15 summons` or `7 low sorcs` or `5 shields` or `2 high sorcs` or `1 fog, 3 shields and 1 summons`
It's that time of the age when I'm starting to think about how things have gone, comments I've read, ideas that have been suggested.
There are three suggestions that I'd like to discuss.
1. Turn the downhit prevention code back on, that prevents kingdom declarations for downhits.
[edit] Feel free to continue to discuss this option, but it would seem that most players thus far, would like to see the code remain off in all games other than bloodbath
2. Configure a maximum size for a Restore, to prevent huge kingdoms just restoring back again after being broken.
[edit] We are still actively discussing this, several interesting ideas have been made for how to tweak this system
3. Add a time-based period of protection to the beginning of the age, a bit like you had at the start of LMS/LQS/LGS
[edit] Feel free to continue to discuss this option, but it would seem that most players thus far, do not feel that this is an option that should be pursued at this time
TWO ADDITIONAL QUESTIONS
4. Should you be unable to restore for 24 hours after sending a cash caravan?
5. Should Restore take away most of your Elan? i.e leave you with 500 elan?
note: 300 Elan = `15 summons` or `7 low sorcs` or `5 shields` or `2 high sorcs` or `1 fog, 3 shields and 1 summons`
Programming is 10% science, 25% ingenuity and 65% getting the ingenuity to work with the science
Wars of Tonan (Monarchy Inspired Miniatures)
Armatures for Sculpting Miniatures
Wars of Tonan (Monarchy Inspired Miniatures)
Armatures for Sculpting Miniatures
Re: v2.5 tweak ideas - discussion thread
Cool Ideas Kaz. I like them. Maybe the size cap on restore could be related to the tithe cap numbers or something? Sweet, thanks for sharing.
~WheEeEeEeEeEeEeEeEeEeEeEeEeEeEeEeEeEe!!!!!!!!!!!!!!!!!!!!!!!!~
MF Mad Flame
Re: v2.5 tweak ideas - discussion thread
I"ll be honest I don't like the first and the last one.
The no hitting down rule seems pointless to me, with how easy it is to manipulate your networth(which is what we are ranked on) by hiring or firing troops, someone can be much bigger then someone, and downsize then hit, then refluff. In addition, it keeps people from being able to keep me in check. All age there was a group don't remember who, who would take 2-3 hits on my realms over and over and over, and it kept me from growing to a decent size till I got lucky and found a NPC that I could kill and fluffed nothing but forts after taking 1k acres. Then they couldn't break me with ease which allowed me to go back to my evilness but with out that constant hitting I would of caused more damage to their faith by killing more of them, and taking that tactic away from someone is pointless.
It also makes it so a guild at the top of the ranks can't "finish" the age by doing a sweep and making themselves untouchable. Or vise versa a smaller guild attack them but doesn't declare but on single kingdoms, the larger bigger guild can't do anything as a team cause they didn't declare as a guild.
As for the time based NP protection - How is this any differnet then a turn based new player protection? Unless you plan to turn off turned based protection and after x number of hours your out of protection then I'm ok with this. Cause there are a handful of kingdoms I could kill off that are sitting in protection status cause they joined and didn't do anything after joining. but if your planning to have both, all your doing is limiting the amount of tactics that can be used to gain an advantage in an age. You saying, no one can attack each other till we are all at 15k acres fullly built with 3k elan in the bank, cause we are giving everyone a xx number of days to build before we can war.
The more tactics you limit the less enjoyable the game becomes because the game is all about figuring out ways to win, tactics.
A maxium for restore is a good idea, this will give people who take a risk and go after the large kingdom guilds something to aim for, you kill the king he can't just come back the next day as king.
The no hitting down rule seems pointless to me, with how easy it is to manipulate your networth(which is what we are ranked on) by hiring or firing troops, someone can be much bigger then someone, and downsize then hit, then refluff. In addition, it keeps people from being able to keep me in check. All age there was a group don't remember who, who would take 2-3 hits on my realms over and over and over, and it kept me from growing to a decent size till I got lucky and found a NPC that I could kill and fluffed nothing but forts after taking 1k acres. Then they couldn't break me with ease which allowed me to go back to my evilness but with out that constant hitting I would of caused more damage to their faith by killing more of them, and taking that tactic away from someone is pointless.
It also makes it so a guild at the top of the ranks can't "finish" the age by doing a sweep and making themselves untouchable. Or vise versa a smaller guild attack them but doesn't declare but on single kingdoms, the larger bigger guild can't do anything as a team cause they didn't declare as a guild.
As for the time based NP protection - How is this any differnet then a turn based new player protection? Unless you plan to turn off turned based protection and after x number of hours your out of protection then I'm ok with this. Cause there are a handful of kingdoms I could kill off that are sitting in protection status cause they joined and didn't do anything after joining. but if your planning to have both, all your doing is limiting the amount of tactics that can be used to gain an advantage in an age. You saying, no one can attack each other till we are all at 15k acres fullly built with 3k elan in the bank, cause we are giving everyone a xx number of days to build before we can war.
The more tactics you limit the less enjoyable the game becomes because the game is all about figuring out ways to win, tactics.
A maxium for restore is a good idea, this will give people who take a risk and go after the large kingdom guilds something to aim for, you kill the king he can't just come back the next day as king.
- Aeropagitica
- Explorer
- Posts: 323
- Joined: Mon Mar 08, 2010 11:13 pm
- Location: Wilmington, NC
- Contact:
Re: v2.5 tweak ideas - discussion thread
Good thoughts.
1. Downhit protection: Witnessing how Bloodbath went, Whether out of necessity for lack of viable opponents or what, down hits were annoying and I simply chose not to continue playing. In Guilds, it wasn't nearly so abused. Population controls have a lot to do with that, as does, in Guilds, we tend to police ourselves to a degree if a down-hit is too flagrant. I was never sad about down-hit rules. the 90% land requirement was a fine rule, in my opinion.
2. Igneous had an interesting idea regarding reset, but I have another. Regarding reset, if you want to change it, scale it based on worth/value. Right now, it's what, 20% of your land lost to the restore gods. What if after 20k acres, that 20% begins to increase, some linear model to say, at 100k acres, 50% is the cost to restore. Granted, this ratio is only realistic for the Guilds game, but some form of scaling penalty for restore could be feasible across all games, with a built in hard-cap.
3. Not really interested in additional early game protections. Granted, one of my strengths is my early game build techniques, so this would only hurt me. With war-declarations being turned off for unguilded though, still, I see no point to expanding additional protections.
1. Downhit protection: Witnessing how Bloodbath went, Whether out of necessity for lack of viable opponents or what, down hits were annoying and I simply chose not to continue playing. In Guilds, it wasn't nearly so abused. Population controls have a lot to do with that, as does, in Guilds, we tend to police ourselves to a degree if a down-hit is too flagrant. I was never sad about down-hit rules. the 90% land requirement was a fine rule, in my opinion.
2. Igneous had an interesting idea regarding reset, but I have another. Regarding reset, if you want to change it, scale it based on worth/value. Right now, it's what, 20% of your land lost to the restore gods. What if after 20k acres, that 20% begins to increase, some linear model to say, at 100k acres, 50% is the cost to restore. Granted, this ratio is only realistic for the Guilds game, but some form of scaling penalty for restore could be feasible across all games, with a built in hard-cap.
3. Not really interested in additional early game protections. Granted, one of my strengths is my early game build techniques, so this would only hurt me. With war-declarations being turned off for unguilded though, still, I see no point to expanding additional protections.
VIVA NIR!
Re: v2.5 tweak ideas - discussion thread
I still think restore needs a longer KO period. I liked the 72 hour bug at the beginning on the age, that actually give the restore more impact. In this last war with Barnabas and NIP/G crushing a kingdom was pretty ineffective, they just came back 48 hours later with full turns...which is how long it takes to get full turns. The reduction in land needs to be tuned up a bit also.
IMO the 48 hour protection, 80% land, 75% building should be tuned to more like 72 hours protection, 70% land, 65% buildings.
That way when my elven gets crushed he doesn't just inspire for cash, send it to an ally and restore and come back and get almost back to where he started one turn cycle later... That felt more like a successful defense than getting destroyed. Both sides at the end were just flailing at each other rather uselessly since restoring a 19k acre kingdom you can capture the built acres back in only a few attacks but you get crushed easily and restoring a 45k acre kingdom takes a bit more to capture the built acres back but you can crush through a couple 19k acre kingdoms to do so...
IMO the 48 hour protection, 80% land, 75% building should be tuned to more like 72 hours protection, 70% land, 65% buildings.
That way when my elven gets crushed he doesn't just inspire for cash, send it to an ally and restore and come back and get almost back to where he started one turn cycle later... That felt more like a successful defense than getting destroyed. Both sides at the end were just flailing at each other rather uselessly since restoring a 19k acre kingdom you can capture the built acres back in only a few attacks but you get crushed easily and restoring a 45k acre kingdom takes a bit more to capture the built acres back but you can crush through a couple 19k acre kingdoms to do so...
Re: v2.5 tweak ideas - discussion thread
1. Please no downhit protection. With the number of coalition wars happening, it'll only make planning out attacks a gigantic flustermuck.
2. Something needs to be done about restore, because as it stands a group can become entrenched at the top such that even completely destroying them would only make them win by slightly less. Take NIR. They are great players with well-built kingdoms. If everyone in the non-Angie game dedicated themselves to dethroning them it would take what, 3-4 restore cycles?
3. No opinion on this one.
2. Something needs to be done about restore, because as it stands a group can become entrenched at the top such that even completely destroying them would only make them win by slightly less. Take NIR. They are great players with well-built kingdoms. If everyone in the non-Angie game dedicated themselves to dethroning them it would take what, 3-4 restore cycles?
3. No opinion on this one.
The Red Ranks
Bringing gravitas to dick jokes since 2013
Bringing gravitas to dick jokes since 2013
- Reylan Talonspyre
- Teacher
- Posts: 537
- Joined: Wed Sep 30, 2009 3:26 am
- Contact:
Re: v2.5 tweak ideas - discussion thread
In Guilds, I am against downhit protection for all the reasons Stee said.
In Guilds, I am for restore being capped out at 18,000 acres. I say this because I restored a lot this age, thus far. I hovered between 14,000 and 18,000 acres. This is a pretty standard kingdom and makes for a good place where the kingdom can be useful again without being totally obliterated or useless.
In Guilds, I am absolutely against a start time. It isn't necessary. I know there were some early wars this age that may have dampened the fun of some players, but it is policed well by our own people. All you are really doing is putting a date out there that we all have to be online to either attack or defend against attacks. I would liken it to the launch of an expansion for World of Warcraft. Bad news all around. At least our server won't crash.
I added the "In Guilds" part to each one because this is the game I play. I can see down hit protection for more "Solo-Like" games.
In Guilds, I am for restore being capped out at 18,000 acres. I say this because I restored a lot this age, thus far. I hovered between 14,000 and 18,000 acres. This is a pretty standard kingdom and makes for a good place where the kingdom can be useful again without being totally obliterated or useless.
In Guilds, I am absolutely against a start time. It isn't necessary. I know there were some early wars this age that may have dampened the fun of some players, but it is policed well by our own people. All you are really doing is putting a date out there that we all have to be online to either attack or defend against attacks. I would liken it to the launch of an expansion for World of Warcraft. Bad news all around. At least our server won't crash.
I added the "In Guilds" part to each one because this is the game I play. I can see down hit protection for more "Solo-Like" games.
I think I would make a great pope.
Gatekeepers
Gatekeepers
- Jokingjoe
- Second Centurion
- Posts: 1204
- Joined: Fri Jan 22, 2010 7:35 pm
- Location: New Bern, NC
- Contact:
Re: v2.5 tweak ideas - discussion thread
1. Dauthi--I'm not sure which side you're supporting on the downhit code. Guild war could still be waged w/o personal declarations and if someone smaller attacked you or an ally, you could still declare as normal. I can see Stee's concern over ability to declare in a coaltion style guild war, but as Aero said, the downhit code wasn't really abused in Guilds like it was in Bloodbath. However, to alleviate the coalition war issues you're concerned about, perhaps Kaz could code in the ability to have multiple guild war decs active at once?
2. Restore is still tricky in my head. Properly used, it is very difficult to knock people down over and over to actually reduce their land. I myself mis-read the networth logs this morning and missed an op to take out a big player in bloodbath as he came out of restore protection and got hammered for my trouble. Perhaps one option might be for the number of hours of Restore Protection to be visible to potential enemies to allow for timely follow-up assaults?
3. I don't see the need to inhibit a player/guild who wants to blitz at the beginning of an age. Players sacrifice a lot of turns to make an early war which can easily be overcome by a smart builder. As Aero said, with the war protections available to non-guilded, if you're afraid of an early war, don't join a guild until you're ready.
2. Restore is still tricky in my head. Properly used, it is very difficult to knock people down over and over to actually reduce their land. I myself mis-read the networth logs this morning and missed an op to take out a big player in bloodbath as he came out of restore protection and got hammered for my trouble. Perhaps one option might be for the number of hours of Restore Protection to be visible to potential enemies to allow for timely follow-up assaults?
3. I don't see the need to inhibit a player/guild who wants to blitz at the beginning of an age. Players sacrifice a lot of turns to make an early war which can easily be overcome by a smart builder. As Aero said, with the war protections available to non-guilded, if you're afraid of an early war, don't join a guild until you're ready.
Re: v2.5 tweak ideas - discussion thread
Joking,
To make it simpler. I'm against it. 100% against it. Would consider not playing for the age if it is added.
Others said what I was trying to say better.
To make it simpler. I'm against it. 100% against it. Would consider not playing for the age if it is added.
Others said what I was trying to say better.
Re: v2.5 tweak ideas - discussion thread
Just to echo some of the comments above, I like the restore function. But doing uphits puts you in a position that you have to kill people twice to potentially bring them down. Although looking at the rankings now, we'd probably have to kill them three times 
"Man will never be free until the last king is strangled with the entrails of the last priest"
Contactable on gtalk & msn via sshagent @ gmail . com
Contactable on gtalk & msn via sshagent @ gmail . com
- Kaz
- Administrator
- Posts: 2614
- Joined: Thu Sep 24, 2009 1:27 am
- Location: The Vinyards of Fernabergia
- Tempers Ball Posts: 3873
- Tempers Ball/Braggarts Hall Alt: Kaz
- Contact:
Re: v2.5 tweak ideas - discussion thread
Original question still stands, but lets start to tailor responses more towards Restore.
So, is it safe to assume the following:
Downhit protection
Leave it off in all games with the exception of Bloodbath, and future solo style games (basically as it was originally designed)
Not required. (Remember this when you consider bitching about being attacked at the start of the age
)
Max Restore
Generally agreed upon, but different ideas on how to implement and where to limit. Options suggested so far.
So, is it safe to assume the following:
Downhit protection
Leave it off in all games with the exception of Bloodbath, and future solo style games (basically as it was originally designed)
- MUltiple Guild War Decs (is on the list but is slightly more complicated to actually impliment than it seems. Wont be v2.5)
Not required. (Remember this when you consider bitching about being attacked at the start of the age
Max Restore
Generally agreed upon, but different ideas on how to implement and where to limit. Options suggested so far.
- 18,000 acres (guilds) other games might need a different max size.
- Based on Tithe Pool : would mean 45k for guilds
- Scaling : Reduction increases as kingdom gets bigger.
Programming is 10% science, 25% ingenuity and 65% getting the ingenuity to work with the science
Wars of Tonan (Monarchy Inspired Miniatures)
Armatures for Sculpting Miniatures
Wars of Tonan (Monarchy Inspired Miniatures)
Armatures for Sculpting Miniatures
- Kaz
- Administrator
- Posts: 2614
- Joined: Thu Sep 24, 2009 1:27 am
- Location: The Vinyards of Fernabergia
- Tempers Ball Posts: 3873
- Tempers Ball/Braggarts Hall Alt: Kaz
- Contact:
Re: v2.5 tweak ideas - discussion thread
Scaling would seem to sound like the most interesting way of implementing things. However, there is one issue that comes with scaling. Basically at some point having less land means a bigger restore than having more land. I've tried jumping down in 1000 to 250 land increments and decreasing restore size by 5% to 1% increments, and whatever I do, eventually we hit a point where it would be more efficient to downsize a few acres and 'then' hit restore.
e.g.
<= 1000 acres 99%
<= 2000 acres 98%
<= 3000 acres 97%
<= 4000 acres 96%
<= 5000 acres 95%
<= 6000 acres 94%
<= 7000 acres 93%
<= 8000 acres 92%
<= 9000 acres 91%
<= 10000 acres 90%
<= 11000 acres 89%
<= 12000 acres 88%
... etc
This works for a while until you reach the 20,000 acre restore, then you start to get out of sync every 10,000 acres
20,000 = 80% = 16,000
20,250 = 79% = 15,998 (should be larger than 16,000)
21,000 = 79% = 16,590
21,250 = 78% = 16,575 (should be larger than 16,590)
Only way around that would be to drop from 1% increments to 0.9%, then later to 0.8% etc etc etc
Eventually the curve would pretty much straighten out, so the 'cap' would be a percentage rather than a land total. That percentage would probably be too high.
e.g.
<= 1000 acres 99%
<= 2000 acres 98%
<= 3000 acres 97%
<= 4000 acres 96%
<= 5000 acres 95%
<= 6000 acres 94%
<= 7000 acres 93%
<= 8000 acres 92%
<= 9000 acres 91%
<= 10000 acres 90%
<= 11000 acres 89%
<= 12000 acres 88%
... etc
This works for a while until you reach the 20,000 acre restore, then you start to get out of sync every 10,000 acres
20,000 = 80% = 16,000
20,250 = 79% = 15,998 (should be larger than 16,000)
21,000 = 79% = 16,590
21,250 = 78% = 16,575 (should be larger than 16,590)
Only way around that would be to drop from 1% increments to 0.9%, then later to 0.8% etc etc etc
Eventually the curve would pretty much straighten out, so the 'cap' would be a percentage rather than a land total. That percentage would probably be too high.
Programming is 10% science, 25% ingenuity and 65% getting the ingenuity to work with the science
Wars of Tonan (Monarchy Inspired Miniatures)
Armatures for Sculpting Miniatures
Wars of Tonan (Monarchy Inspired Miniatures)
Armatures for Sculpting Miniatures
Re: v2.5 tweak ideas - discussion thread
Do it like the US tax code. I.E. First 10000 built acres gets 80% restored, acres between 10000 and 20000 get 70% restored, acres beyond 20k get 25% restored.
It would work as follows:
If kingdom at 9k largest kingdom size (built) restored it comes back at 7.2k (80% of 9k)
If a kingdom at 17k built acres restored it would come back at 12.9k (80% of the first 10k + 70% of the remaining 7k)
If a kingdom at 60k built acres restored it would come back at 25k built. (80% of first 10k +70% of next 10k + 25% of remaining 40k)
This makes it so if you have more built acres you would always come back with more than someone with less built acres, just not necessarily a lot more as more of the acres gets "taxed" at the higher rate. And while it sounds complicated it is pretty simple to calculate
(personally I think the first 20k should have a bit lower restore rate than the 75% this model and the current system gives though as I stated before...but that is another issue)
It would work as follows:
If kingdom at 9k largest kingdom size (built) restored it comes back at 7.2k (80% of 9k)
If a kingdom at 17k built acres restored it would come back at 12.9k (80% of the first 10k + 70% of the remaining 7k)
If a kingdom at 60k built acres restored it would come back at 25k built. (80% of first 10k +70% of next 10k + 25% of remaining 40k)
This makes it so if you have more built acres you would always come back with more than someone with less built acres, just not necessarily a lot more as more of the acres gets "taxed" at the higher rate. And while it sounds complicated it is pretty simple to calculate
(personally I think the first 20k should have a bit lower restore rate than the 75% this model and the current system gives though as I stated before...but that is another issue)
- Kaz
- Administrator
- Posts: 2614
- Joined: Thu Sep 24, 2009 1:27 am
- Location: The Vinyards of Fernabergia
- Tempers Ball Posts: 3873
- Tempers Ball/Braggarts Hall Alt: Kaz
- Contact:
Re: v2.5 tweak ideas - discussion thread
Looking at Guilds, Domination and Bloodbath, the primary cluster tends to be around 20-25k acres. Even with larger turn-rates, bigger tithe-pools etc that seems to be the 'average' kingdom size.
I personally think that if we were to just to a direct cap of around 30k, with some building destroyed as usual to leave a bit of open land, it would probably work pretty well. Big kingdoms would be reduced drastically, but they'd still be among the better average kingdoms. Being reduced to 18k (per Reylan's suggestion), means that no matter how well you built or played, you always restore below the cluster.
That would mean the following
<= 37,500 acres
80% Land
75% Buildings
e.g.
37,500 fully built becomes 30,000 acres, 28125 built
> 37,500 acres
30,000 acres (capped)
75% Buildings or 28125 built (capped)
Darnivan's suggestion to Aero's idea is another good one. I've had a play with how it might look (using slightly different stat ranges).
Total Land
First 5000 acres = Tax free
Next 5000 acres Lose 10% in Restore Tax
Next 10000 acres Lose 25% in Restore Tax
Next 20000 acres Lose 50% in Restore Tax
Any additional acres Lose 75% in Restore Tax
5,000 = 5000 (100%)
10,000 = 5000 + 4500 = 9500 (95%)
20,000 = 5000 + 4500 + 7500 = 17000 (85%)
30,000 = 5000 + 4500 + 7500 + 5000 = 22000 (73.33%)
40,000 = 5000 + 4500 + 7500 + 10000 = 27000 (67.5%)
50,000 = 5000 + 4500 + 7500 + 10000 + 2500 = 29500 (59%)
60,000 = 5000 + 4500 + 7500 + 10000 + 5000 = 32000 (53.33%)
70,000 = 5000 + 4500 + 7500 + 10000 + 7500 = 34500 (49.29%)
80,000 = 5000 + 4500 + 7500 + 10000 + 1000 = 37000 (46.25%)
90,000 = 5000 + 4500 + 7500 + 10000 + 12500 = 39500 (43.88%)
100,000 = 5000 + 4500 + 7500 + 10000 + 15000 = 42000 (42%)
150,000 = 5000 + 4500 + 7500 + 10000 + 27500 = 54500 (36.33%)
200,000 = 5000 + 4500 + 7500 + 10000 + 40000 = 67000 (33.5%)
250,000 = 5000 + 4500 + 7500 + 10000 + 52500 = 79500 (31.8%)
Built Land
First 5000 acres = Lose 5% in Restore Tax
Next 5000 acres Lose 15% in Restore Tax
Next 10000 acres Lose 30% in Restore Tax
Next 20000 acres Lose 55% in Restore Tax
Any additional acres Lose 77.5% in Restore Tax
5,000 = 4750 (95%)
10,000 = 4750 + 4250 = 9000 (90%)
20,000 = 4750 + 4250 + 7000 = 16000 (80%)
30,000 = 4750 + 4250 + 7000 + 4500 = 20500 (68.33%)
40,000 = 4750 + 4250 + 7000 + 9000 = 25000 (62.5%)
50,000 = 4750 + 4250 + 7000 + 9000 + 2250 = 27250 (54.5%)
60,000 = 4750 + 4250 + 7000 + 9000 + 4500 = 29500 (49.17%)
70,000 = 4750 + 4250 + 7000 + 9000 + 6750 = 31750 (45.36%)
80,000 = 4750 + 4250 + 7000 + 9000 + 9000 = 34000 (42.5%)
90,000 = 4750 + 4250 + 7000 + 9000 + 11250 = 36250 (40.28%)
100,000 = 4750 + 4250 + 7000 + 9000 + 13500 = 38500 (38.5%)
150,000 = 4750 + 4250 + 7000 + 9000 + 24750 = 49750 (33.17%)
200,000 = 4750 + 4250 + 7000 + 9000 + 36000 = 61000 (30.5%)
250,000 = 4750 + 4250 + 7000 + 9000 + 47250 = 72250 (28.9%)
I personally think that if we were to just to a direct cap of around 30k, with some building destroyed as usual to leave a bit of open land, it would probably work pretty well. Big kingdoms would be reduced drastically, but they'd still be among the better average kingdoms. Being reduced to 18k (per Reylan's suggestion), means that no matter how well you built or played, you always restore below the cluster.
That would mean the following
<= 37,500 acres
80% Land
75% Buildings
e.g.
37,500 fully built becomes 30,000 acres, 28125 built
> 37,500 acres
30,000 acres (capped)
75% Buildings or 28125 built (capped)
Darnivan's suggestion to Aero's idea is another good one. I've had a play with how it might look (using slightly different stat ranges).
Total Land
First 5000 acres = Tax free
Next 5000 acres Lose 10% in Restore Tax
Next 10000 acres Lose 25% in Restore Tax
Next 20000 acres Lose 50% in Restore Tax
Any additional acres Lose 75% in Restore Tax
5,000 = 5000 (100%)
10,000 = 5000 + 4500 = 9500 (95%)
20,000 = 5000 + 4500 + 7500 = 17000 (85%)
30,000 = 5000 + 4500 + 7500 + 5000 = 22000 (73.33%)
40,000 = 5000 + 4500 + 7500 + 10000 = 27000 (67.5%)
50,000 = 5000 + 4500 + 7500 + 10000 + 2500 = 29500 (59%)
60,000 = 5000 + 4500 + 7500 + 10000 + 5000 = 32000 (53.33%)
70,000 = 5000 + 4500 + 7500 + 10000 + 7500 = 34500 (49.29%)
80,000 = 5000 + 4500 + 7500 + 10000 + 1000 = 37000 (46.25%)
90,000 = 5000 + 4500 + 7500 + 10000 + 12500 = 39500 (43.88%)
100,000 = 5000 + 4500 + 7500 + 10000 + 15000 = 42000 (42%)
150,000 = 5000 + 4500 + 7500 + 10000 + 27500 = 54500 (36.33%)
200,000 = 5000 + 4500 + 7500 + 10000 + 40000 = 67000 (33.5%)
250,000 = 5000 + 4500 + 7500 + 10000 + 52500 = 79500 (31.8%)
Built Land
First 5000 acres = Lose 5% in Restore Tax
Next 5000 acres Lose 15% in Restore Tax
Next 10000 acres Lose 30% in Restore Tax
Next 20000 acres Lose 55% in Restore Tax
Any additional acres Lose 77.5% in Restore Tax
5,000 = 4750 (95%)
10,000 = 4750 + 4250 = 9000 (90%)
20,000 = 4750 + 4250 + 7000 = 16000 (80%)
30,000 = 4750 + 4250 + 7000 + 4500 = 20500 (68.33%)
40,000 = 4750 + 4250 + 7000 + 9000 = 25000 (62.5%)
50,000 = 4750 + 4250 + 7000 + 9000 + 2250 = 27250 (54.5%)
60,000 = 4750 + 4250 + 7000 + 9000 + 4500 = 29500 (49.17%)
70,000 = 4750 + 4250 + 7000 + 9000 + 6750 = 31750 (45.36%)
80,000 = 4750 + 4250 + 7000 + 9000 + 9000 = 34000 (42.5%)
90,000 = 4750 + 4250 + 7000 + 9000 + 11250 = 36250 (40.28%)
100,000 = 4750 + 4250 + 7000 + 9000 + 13500 = 38500 (38.5%)
150,000 = 4750 + 4250 + 7000 + 9000 + 24750 = 49750 (33.17%)
200,000 = 4750 + 4250 + 7000 + 9000 + 36000 = 61000 (30.5%)
250,000 = 4750 + 4250 + 7000 + 9000 + 47250 = 72250 (28.9%)
Programming is 10% science, 25% ingenuity and 65% getting the ingenuity to work with the science
Wars of Tonan (Monarchy Inspired Miniatures)
Armatures for Sculpting Miniatures
Wars of Tonan (Monarchy Inspired Miniatures)
Armatures for Sculpting Miniatures
Re: v2.5 tweak ideas - discussion thread
With those numbers restore for kingdoms under 20k are still too strong, making attacking them have almost no effect. While I don't mind having the kingdoms recover that would be problematic in a longer war like the last wars where kingdoms were restoring and coming back into the fight. A war between guilds with small kingdoms that doesn't end in a decisive victory would become messy as kingdoms could only get bigger so you would only attack to capture land not damage the enemy. Burning/sorceing a kingdoms buildings would be a pointless waste of turns...at least if you destroy more than like 20% of their buildings. Some of the wars ended prematurely this age with guilds giving up when they probably would have won a protracted fight using restore. Maybe they didn't want to fight the protracted war or maybe they didn't realized that they were winning but the wars ended and watching I was left confused why they gave up so quick but as people get more experience using restore and realize how cheep and easy it is and the massive benefit I doubt they will want to give up so quick. Really the first actual experiences of its power was in these last wars with kingdoms like my elven and others coming out of restore just as strong or stronger after using their turns saved up during restore than before. I was getting a bit frustrated at the 20k+ acre kingdoms we would destroy, they would restore and attack and be right back around 25k acres again and we would have to destroy them again. The only reason that war ended was while we were making no progress beating down those 20k acre kingdoms over and over they were also unable to do anything against our massive kingdoms so those were just getting fed bigger and bigger.
The only good (least disruptive, easy to implement) solution I can think of to suggest would be to increase the protection period, if kingdoms in restore were out of the fight for longer than it would make destroying a kingdom have a meaningful effect in a war rather than the minor turn cost followed by a beneficial 2 day safe period that you can't be attacked in while you build up turns. I think restoring should at least take a kingdoms effectively out of the war for 48 hours (while right now since 48 hours is the time it takes for the kingdom to save turns it only really takes them out of the war for the number of turns they lost going into it). If the protection time was 72 hours then they would be forced to use some of their turns in the protection for reduced benefit and wouldn't be able to rejoin the war for an extra 24 hours making the restore penalty those 24 hours+the turn cost to restore.
The kingdoms would still come back just as big, but with the longer period out of the war the fighting strength of the guild is weakened more so once a guild had too many kingdoms in restore the kingdoms remaining would be more easily focused down before the restoring kingdoms get back giving an advantage to the guild not restoring rather than to the guild restoring (which is effectively how it is now).
That is my opinion anyway. If you want to encourage longer wars maybe it is better the way it is. I just don't think it is very satisfying to sorcery a kingdom down to just have it restore back to nearly full strength and come back and crush you 2 days later like you didn't do anything at all to it. Restore now works like using 36 turns to cast an impregnable 48 shield over 75% of your past kingdom destroying the other 25% and wiping out your cash. For such a low cost it is silly not to do it during a war or not if you have lost more than like 30% of your buildings.
The only good (least disruptive, easy to implement) solution I can think of to suggest would be to increase the protection period, if kingdoms in restore were out of the fight for longer than it would make destroying a kingdom have a meaningful effect in a war rather than the minor turn cost followed by a beneficial 2 day safe period that you can't be attacked in while you build up turns. I think restoring should at least take a kingdoms effectively out of the war for 48 hours (while right now since 48 hours is the time it takes for the kingdom to save turns it only really takes them out of the war for the number of turns they lost going into it). If the protection time was 72 hours then they would be forced to use some of their turns in the protection for reduced benefit and wouldn't be able to rejoin the war for an extra 24 hours making the restore penalty those 24 hours+the turn cost to restore.
The kingdoms would still come back just as big, but with the longer period out of the war the fighting strength of the guild is weakened more so once a guild had too many kingdoms in restore the kingdoms remaining would be more easily focused down before the restoring kingdoms get back giving an advantage to the guild not restoring rather than to the guild restoring (which is effectively how it is now).
That is my opinion anyway. If you want to encourage longer wars maybe it is better the way it is. I just don't think it is very satisfying to sorcery a kingdom down to just have it restore back to nearly full strength and come back and crush you 2 days later like you didn't do anything at all to it. Restore now works like using 36 turns to cast an impregnable 48 shield over 75% of your past kingdom destroying the other 25% and wiping out your cash. For such a low cost it is silly not to do it during a war or not if you have lost more than like 30% of your buildings.
Re: v2.5 tweak ideas - discussion thread
I also thought of a different implementation for restore that could also make MUCH better for in war restores while not effecting out of war restores much.
Right now restore takes 72 turns and the restored kingdom has 36 turns and 10k cash and 48 hours protection with reduced effectiveness of building, training, inspiring for cash.
My idea is to have restore take 72 turns and the restored kingdom has 72 turns, 10k cash, and 72 turns in which it cannot attack, but can be attacked and cannot restore again for 72 hours. This would force the kingdom to fort defensively with those 72 turns immediately after the restore and would be vulnerable to attack while saving up turns to come back into the war. Thus restoring in a war isn't so safe as you could be burned or attacked again right away. Out of war restores actually save 36 turns, but not being at war with anyone that wouldn't matter too much. Of course the details could be altered however you liked if you wanted to use that solution.
With this solution there would have been no way my elven would have survived at 36k acres to get enough turns to take land to get back large enough to defend itself.
Right now restore takes 72 turns and the restored kingdom has 36 turns and 10k cash and 48 hours protection with reduced effectiveness of building, training, inspiring for cash.
My idea is to have restore take 72 turns and the restored kingdom has 72 turns, 10k cash, and 72 turns in which it cannot attack, but can be attacked and cannot restore again for 72 hours. This would force the kingdom to fort defensively with those 72 turns immediately after the restore and would be vulnerable to attack while saving up turns to come back into the war. Thus restoring in a war isn't so safe as you could be burned or attacked again right away. Out of war restores actually save 36 turns, but not being at war with anyone that wouldn't matter too much. Of course the details could be altered however you liked if you wanted to use that solution.
With this solution there would have been no way my elven would have survived at 36k acres to get enough turns to take land to get back large enough to defend itself.
Re: v2.5 tweak ideas - discussion thread
1. Turn the downhit prevention code back on, that prevents kingdom declarations for downhits.
I think my opinions of this have been made fairly clear in bloodbath. That being said I entirely understand the difficulties it could create here in guilds, and can see less need for it in guilds than in solo style games. Again, that idea of strategy and self-policing behaviours can occur over here because of the larger, more active player base.
2. Configure a maximum size for a Restore, to prevent huge kingdoms just restoring back again after being broken.
I don't have any suggestions here per se, however I am interested in seeing what the outcome will be. I haven't been playing in guilds long enough to truely see how restoring effects things. I can say however, that the restore function in bloodbath has basically negated the idea of actually having a war. I have yet to see a strike/counter strike battle in bloodbath. Simply being hit and then restoring seems to be the name of the game.
3. Add a time-based period of protection to the beginning of the age, a bit like you had at the start of LMS/LQS/LGS
Again, I don't have any suggestions per se. I didn't see the early hits here as I didn't join until late in the age. I remember in the past that early hitting was judged in the boards and self-policing occured... I didn't have any issues with his in bloodbath, frankly I didn't even have any wars outside of NPC's for the first few weeks.
I think my opinions of this have been made fairly clear in bloodbath. That being said I entirely understand the difficulties it could create here in guilds, and can see less need for it in guilds than in solo style games. Again, that idea of strategy and self-policing behaviours can occur over here because of the larger, more active player base.
2. Configure a maximum size for a Restore, to prevent huge kingdoms just restoring back again after being broken.
I don't have any suggestions here per se, however I am interested in seeing what the outcome will be. I haven't been playing in guilds long enough to truely see how restoring effects things. I can say however, that the restore function in bloodbath has basically negated the idea of actually having a war. I have yet to see a strike/counter strike battle in bloodbath. Simply being hit and then restoring seems to be the name of the game.
3. Add a time-based period of protection to the beginning of the age, a bit like you had at the start of LMS/LQS/LGS
Again, I don't have any suggestions per se. I didn't see the early hits here as I didn't join until late in the age. I remember in the past that early hitting was judged in the boards and self-policing occured... I didn't have any issues with his in bloodbath, frankly I didn't even have any wars outside of NPC's for the first few weeks.
-}}}Dulcius ex Asperis >
Gatekeepers...SUCK?
Gatekeepers...SUCK?
- Kaz
- Administrator
- Posts: 2614
- Joined: Thu Sep 24, 2009 1:27 am
- Location: The Vinyards of Fernabergia
- Tempers Ball Posts: 3873
- Tempers Ball/Braggarts Hall Alt: Kaz
- Contact:
Re: v2.5 tweak ideas - discussion thread
Darnivan, I'm going to respond to your second post first.
Basically this idea, although interesting, does not fit with the idea behind restore at all. Essentially your suggesting a system that would restore the negative feelings that accompany having your kingdom smashed.
This game will never have functionality that prevents a kingdom from attacking, while at the same time leaves them vulnerable to attack.
Also, with the save a restore is based on limited to a rolling 72 hour window, there will never be a 72 hour block on restoring.
Essentially you're suggestion would lead to this scenario
* Huge Kingdom flattens small kingdom
* Small Kingdom restores to slightly smaller kingdom
* Huge Kingdom flattens again
* Small Kingdom prevented from restoring
* Small Kingdom stays flattened
It's not really all that different from how the game works without the restore feature, as I see it, it just adds 'another' reason for the defender to feel aggravated, because they've now been smashed twice instead of just once.
-----------------------
The whole point of the restore system is to take away the feeling of the game having been a pointless waste of time, after logging in to find weeks or months of turns being totally obliterated in a short space of time. This is an issue which plagues kingdom-based strategy games.
I played Command & Conquer Tiberium Alliances for a short while, and although the game is totally different conceptually, it helped me realise that kingdom-based games 'can' still be enjoyable and tactical, without kingdom death occurring. Basically, when another player attacks you they destroy your defences, kill your armies, take your resources, and grow a bit stronger. However, the work you've put into your `kingdom` is not undone, and it essentially heals back to 100% over a short timespan.
This is also essentially how 'most' multi-player 'hero' games work. Your hero might be killed, but the stats you've trained up, adventures you've completed and items you've collected don't get wiped out, like months worth of turns do in the standard style browser-base kingdom game.
Restore is about finding a way that strategy, and progression can still exist in a kingdom-based game, but without being accompanied by that feeling of total loss. Unlike a risk-free idea, our system still has the ability to fail. For example, if you miss that 72 hour window there is no restore available. You also lose turns, and you don't get a 100% restore.
-----------------------
On the subject of a longer restore window, which I'm more than happy to implement if that's what the majority want.
One thing that you're not taking into consideration in your thoughts and calculations, is that - unless you've been killed, and this adds an extra 24 hours protection - you cannot restore if you've attacked in the previous 24 hours.
That means that, other than restoring immediately after a first strike, any kingdom that restores is 'already' out of the war for 72 hours.
The main issue at the moment for most people, isn't really that small kingdoms don't lose enough, it's that large kingdoms are essentially immortal and need to be broken 3 or 4 times to actually reduce them to the same size as the smaller kingdoms breaking them.
If resolving that fairly creates a situation where skill, tactics and strength cannot keep a guild at the top of the scrolls, due to tactical use of drawn out restore systems that favour the weak, then we'll try and think of a way to resolve that next time.
-----------------------
On the subject of war becoming more about taking land than destroying buildings, peasants etc, I'm also worried about the implications.
I'm just not 100% sure how exactly we can implement something that restores the benefits to certain non-military attack options, with the current restore process.
I'm open to suggestions.
What we're currently using, is a quick implementation of a more complex idea that I had ages ago. I'd eventually like to switch to a better restore system like the one we started designing in this thread.
viewtopic.php?f=19&t=1251
Basically this idea, although interesting, does not fit with the idea behind restore at all. Essentially your suggesting a system that would restore the negative feelings that accompany having your kingdom smashed.
This game will never have functionality that prevents a kingdom from attacking, while at the same time leaves them vulnerable to attack.
Also, with the save a restore is based on limited to a rolling 72 hour window, there will never be a 72 hour block on restoring.
Essentially you're suggestion would lead to this scenario
* Huge Kingdom flattens small kingdom
* Small Kingdom restores to slightly smaller kingdom
* Huge Kingdom flattens again
* Small Kingdom prevented from restoring
* Small Kingdom stays flattened
It's not really all that different from how the game works without the restore feature, as I see it, it just adds 'another' reason for the defender to feel aggravated, because they've now been smashed twice instead of just once.
-----------------------
The whole point of the restore system is to take away the feeling of the game having been a pointless waste of time, after logging in to find weeks or months of turns being totally obliterated in a short space of time. This is an issue which plagues kingdom-based strategy games.
I played Command & Conquer Tiberium Alliances for a short while, and although the game is totally different conceptually, it helped me realise that kingdom-based games 'can' still be enjoyable and tactical, without kingdom death occurring. Basically, when another player attacks you they destroy your defences, kill your armies, take your resources, and grow a bit stronger. However, the work you've put into your `kingdom` is not undone, and it essentially heals back to 100% over a short timespan.
This is also essentially how 'most' multi-player 'hero' games work. Your hero might be killed, but the stats you've trained up, adventures you've completed and items you've collected don't get wiped out, like months worth of turns do in the standard style browser-base kingdom game.
Restore is about finding a way that strategy, and progression can still exist in a kingdom-based game, but without being accompanied by that feeling of total loss. Unlike a risk-free idea, our system still has the ability to fail. For example, if you miss that 72 hour window there is no restore available. You also lose turns, and you don't get a 100% restore.
-----------------------
On the subject of a longer restore window, which I'm more than happy to implement if that's what the majority want.
One thing that you're not taking into consideration in your thoughts and calculations, is that - unless you've been killed, and this adds an extra 24 hours protection - you cannot restore if you've attacked in the previous 24 hours.
That means that, other than restoring immediately after a first strike, any kingdom that restores is 'already' out of the war for 72 hours.
The main issue at the moment for most people, isn't really that small kingdoms don't lose enough, it's that large kingdoms are essentially immortal and need to be broken 3 or 4 times to actually reduce them to the same size as the smaller kingdoms breaking them.
If resolving that fairly creates a situation where skill, tactics and strength cannot keep a guild at the top of the scrolls, due to tactical use of drawn out restore systems that favour the weak, then we'll try and think of a way to resolve that next time.
-----------------------
On the subject of war becoming more about taking land than destroying buildings, peasants etc, I'm also worried about the implications.
I'm just not 100% sure how exactly we can implement something that restores the benefits to certain non-military attack options, with the current restore process.
I'm open to suggestions.
What we're currently using, is a quick implementation of a more complex idea that I had ages ago. I'd eventually like to switch to a better restore system like the one we started designing in this thread.
viewtopic.php?f=19&t=1251
Programming is 10% science, 25% ingenuity and 65% getting the ingenuity to work with the science
Wars of Tonan (Monarchy Inspired Miniatures)
Armatures for Sculpting Miniatures
Wars of Tonan (Monarchy Inspired Miniatures)
Armatures for Sculpting Miniatures
Re: v2.5 tweak ideas - discussion thread
The 72 turns that you can't attack are to force the person to use the turns to fort defense rather than being able to immediately attack. They already have the turns, they just need to use them. Thus there should be no period that they can be attacked without being able to attack other than they have no turns. If you wanted you could combine it with a 1 hour protection so they can't be attacked before they have a chance to refortify. The other points is restoring in battle SHOULD be a risk. I still hate the idea of restore being usable mid war. It makes no sense whatsoever but it would be extremely hard to design a catch all that only allows restores after a war for all the wars of varied lengths and circumstances. The point is restore should not be done lightly in a war.
The 72 hours block on restoring is to prevent you from being able to restore back to the same kingdom multiple times or you could restore, suicide attack once you have a few turns, and restore again before the 72 hours is up. That would be begging to be misused. Last age I was able to restore to the same kingdom twice within the period of taking heavy damage on one of my kingdoms... I was able to use the kingdom to feed cash into my bigger surviving kingdom and restore again after enemies resumed sorce attacks after coming out of restore protection, effectively wasting the enemies turns for no damage. That whole interaction of restore with war is damaging to the game in how manipulable it is and how it makes actions that damage the enemy without benefiting yourself pointless. I suppose a better solution than the prevention would be to limit the time restore looks back to the moment of the last restore usage so future restores are based on what happened after the kingdom was restored and not on the kingdom that existed before they restored.
24 hours of time and turns isn't much for use of turns in defense of your kingdom while being attacked so really that is no cost at all. Just now if you don't think you can hold out you would just restore before they break through your defenses and take much land if you are on when they hit...
Restore is good for the life of the game in that people don't lose a month of building in 5 minutes, but the effect it has mid war almost make me quit last age. I stuck it out for this age to see if it might improve but the effect during this last war was just as bad... I have agreed to go barny with aero and jokingjoe next age for faith balance so I'll be sticking it out at least one more age to see if it isn't as bad, but as it is I don't want ever to be in another war long enough for restores to come into effect.
The 72 hours block on restoring is to prevent you from being able to restore back to the same kingdom multiple times or you could restore, suicide attack once you have a few turns, and restore again before the 72 hours is up. That would be begging to be misused. Last age I was able to restore to the same kingdom twice within the period of taking heavy damage on one of my kingdoms... I was able to use the kingdom to feed cash into my bigger surviving kingdom and restore again after enemies resumed sorce attacks after coming out of restore protection, effectively wasting the enemies turns for no damage. That whole interaction of restore with war is damaging to the game in how manipulable it is and how it makes actions that damage the enemy without benefiting yourself pointless. I suppose a better solution than the prevention would be to limit the time restore looks back to the moment of the last restore usage so future restores are based on what happened after the kingdom was restored and not on the kingdom that existed before they restored.
24 hours of time and turns isn't much for use of turns in defense of your kingdom while being attacked so really that is no cost at all. Just now if you don't think you can hold out you would just restore before they break through your defenses and take much land if you are on when they hit...
Restore is good for the life of the game in that people don't lose a month of building in 5 minutes, but the effect it has mid war almost make me quit last age. I stuck it out for this age to see if it might improve but the effect during this last war was just as bad... I have agreed to go barny with aero and jokingjoe next age for faith balance so I'll be sticking it out at least one more age to see if it isn't as bad, but as it is I don't want ever to be in another war long enough for restores to come into effect.
- Kaz
- Administrator
- Posts: 2614
- Joined: Thu Sep 24, 2009 1:27 am
- Location: The Vinyards of Fernabergia
- Tempers Ball Posts: 3873
- Tempers Ball/Braggarts Hall Alt: Kaz
- Contact:
Re: v2.5 tweak ideas - discussion thread
As it currently stands you could restore, come out of RPP, inspire and send cash, then restore the first restore again. But there is a very limited window to pull that off.
You want to take away the ability to send cash before a restore that's easy enough to impliment. It already prevents you from restoring if you've attacked in the last 24 hours, it could do the sa,e if you've sent cash in the last 24 hours.
You could not restore, come out of RPP, attack, and then restore back to the first restore. At least not with the timers in guilds. 48 hours RPP + 24 hours peace means that you'll be rolling back to the kingdom you restored into. Meaning another loss of 20% land and 25% buildings.
I suppose I could add an inability to restore for 24 hours after RPP ends, but as it's such a small window, and we're talking about a restore cap anyway, I don't really see what it would really acheive
There hasn't actually been a propper dragged out war with restore yet, partly because making the decision to restore during war time is still quite a big deal.
I'm personally on the other side of the fence to you. I actually think that a long duration war where both sides keep restoring, could be fun. Certainly more fun than 'first strike wins'.
I'm still not actually sure I understand what you're suggesting with this 72 turns thingy.
If a kingdom restores with 72 turns, and cannot attack (or be attacked) until those 72 turns are up, it's pretty much identical to a 24 hour restore window, but with control over the exact moment RPP ends.
They get 32 extra free turns, and can just wait until they are at full before spending the last turn.
I could have built restore that way, but went for a timed period so that a kingdom didn't get a free shield that it could keep up until it wanted to leave.
With a land cap, the main danger from a restored kingdom is probably sorcery. The only way to resolve that would be to take away Elan during the restore too.
Warriors and scummers need to spend turns generating cash (at a reduced rate) and reforting (at a reduced rate). You can't actually come out of RPP at the moment with 'full' turns and be fully forted with cash to fuel an attack.
You 'are' slightly stronger turn-wise at the end of RPP than I anticipated though, and I might take away those 32 turns that I added. I thought the reductions to BRT, Train-Rate, Inspire & Chant would need a few extra turns.
--------------------------------------
Anyway.... back to the questions this thread was asking, I currently intend to code the tax-based limitation on restore size. I think it'll work the best of the two options under consideration.
Two new questions
- Should you be unable to restore for 24 hours after sending a cash caravan?
- Should Restore take away most of your Elan? e.g. leave you with 500 elan
You want to take away the ability to send cash before a restore that's easy enough to impliment. It already prevents you from restoring if you've attacked in the last 24 hours, it could do the sa,e if you've sent cash in the last 24 hours.
You could not restore, come out of RPP, attack, and then restore back to the first restore. At least not with the timers in guilds. 48 hours RPP + 24 hours peace means that you'll be rolling back to the kingdom you restored into. Meaning another loss of 20% land and 25% buildings.
I suppose I could add an inability to restore for 24 hours after RPP ends, but as it's such a small window, and we're talking about a restore cap anyway, I don't really see what it would really acheive
There hasn't actually been a propper dragged out war with restore yet, partly because making the decision to restore during war time is still quite a big deal.
I'm personally on the other side of the fence to you. I actually think that a long duration war where both sides keep restoring, could be fun. Certainly more fun than 'first strike wins'.
I'm still not actually sure I understand what you're suggesting with this 72 turns thingy.
If a kingdom restores with 72 turns, and cannot attack (or be attacked) until those 72 turns are up, it's pretty much identical to a 24 hour restore window, but with control over the exact moment RPP ends.
They get 32 extra free turns, and can just wait until they are at full before spending the last turn.
I could have built restore that way, but went for a timed period so that a kingdom didn't get a free shield that it could keep up until it wanted to leave.
With a land cap, the main danger from a restored kingdom is probably sorcery. The only way to resolve that would be to take away Elan during the restore too.
Warriors and scummers need to spend turns generating cash (at a reduced rate) and reforting (at a reduced rate). You can't actually come out of RPP at the moment with 'full' turns and be fully forted with cash to fuel an attack.
You 'are' slightly stronger turn-wise at the end of RPP than I anticipated though, and I might take away those 32 turns that I added. I thought the reductions to BRT, Train-Rate, Inspire & Chant would need a few extra turns.
--------------------------------------
Anyway.... back to the questions this thread was asking, I currently intend to code the tax-based limitation on restore size. I think it'll work the best of the two options under consideration.
Two new questions
- Should you be unable to restore for 24 hours after sending a cash caravan?
- Should Restore take away most of your Elan? e.g. leave you with 500 elan
Programming is 10% science, 25% ingenuity and 65% getting the ingenuity to work with the science
Wars of Tonan (Monarchy Inspired Miniatures)
Armatures for Sculpting Miniatures
Wars of Tonan (Monarchy Inspired Miniatures)
Armatures for Sculpting Miniatures
Who is online
Users browsing this forum: No registered users and 5 guests