I saw the first tax report with the new system today for my region of Kuugl on Beluaterra. The Lord has a 50% estate and one knight also has a 50% estate. That knight autopaused yesterday:
Knight paused (22 hours, 29 minutes ago)
Rophlock Spirien (Knight of Kuugl) has been auto-paused due to inactivity. His bonds revert to the realm.
But even though he is paused, he received revenues:
Estate of Size Peasants Tax Collected Knight Share Lord Share
Rophlock 50 % 2559 80 gold 68 gold 12 gold
Jos 50 % 2559 80 gold 80 gold
Region Totals 160 gold 68 gold 92 gold
I believe this is a bug?
Quote from: vonGenf on September 30, 2011, 07:32:47 AM
I saw the first tax report with the new system today for my region of Kuugl on Beluaterra. The Lord has a 50% estate and one knight also has a 50% estate. That knight autopaused yesterday:
Knight paused (22 hours, 29 minutes ago)
Rophlock Spirien (Knight of Kuugl) has been auto-paused due to inactivity. His bonds revert to the realm.
But even though he is paused, he received revenues:
Estate of Size Peasants Tax Collected Knight Share Lord Share
Rophlock 50 % 2559 80 gold 68 gold 12 gold
Jos 50 % 2559 80 gold 80 gold
Region Totals 160 gold 68 gold 92 gold
I believe this is a bug?
Could be, or the responsibility to remove inactive knights may now rest with the Lord. As you can easily kick knights out of their estates now where the old system only had the 3 bad marks path.
surely if they are paused you shouldn't have to kick anything. by definition it's a vacant estate ripe for anyone's taking.
Doesn't look like it currently set the estate vacant when you pause. Could be one of the things still to implement, or it could be on purpose. I would guess it is still to be implemented, but I can see IC reasons to leave it as is.
It looks to me more like something yet to implement.
On a similar matter, we had a knight join Luria Nova, take a estate in Sulorte and then take a estate in Outer Giask. His signature is still "Knight of Sulorte" though he has no longer an estate in there, but in Outer Giask instead.
This little stuff should be fixed with time.
correct, it's not yet implemented. You can fix it easily yourself (kick him out), but it should remove him automatically.
Quote from: Tom on September 30, 2011, 04:01:09 PM
correct, it's not yet implemented. You can fix it easily yourself (kick him out), but it should remove him automatically.
That's what I did for now, thanks.