Closed GoogleCodeExporter closed 9 years ago
It depends on how you've configured the war settings in the config. And which
war type you're using.
Original comment by LlmD...@gmail.com
on 23 Mar 2013 at 11:30
I use normal war type (without the flag).
How can I deactivate it?
Is there any difference if I use the war flag?
Original comment by cortiand...@gmail.com
on 24 Mar 2013 at 12:40
Use /ta toggle war to deactivate non-flag-war.
Read about the differences on the How Towny Works wikipage.
Original comment by LlmD...@gmail.com
on 24 Mar 2013 at 12:44
[deleted comment]
Ok, I tried a few config and I still have two issues:
I'd like to configure a NON-flag-war that works something like:
. admin toggle war
. player must go into enemy territory and they can destroy only fences, doors
and a few other blocks types
. when the plot HPs go to 0, the player should be able to destroy everything
in that plot.
this is the config file I created: http://pastebin.com/8y6bYQqU
THe problem is that enemies, when war is toggled, can already destroy
everyhthing
Original comment by cortiand...@gmail.com
on 27 Mar 2013 at 4:11
Try changing: editable_materials: tnt,fence,ladder,wood_door,iron_door,fire
into: editable_materials: 'tnt,fence,ladder,wood_door,iron_door,fire'
Original comment by LlmD...@gmail.com
on 27 Mar 2013 at 7:22
no, when the server restart (or ta reload), the ' char is removed automatically
from config file.
If I do enable allow_block_griefing, enemies can destroy everything, otherwise
they can destroy nothing.
Original comment by cortiand...@gmail.com
on 4 Apr 2013 at 2:11
This should have been put in as a defect, you would have given us the
config/permissions setup. I'm guessing that you've given too many permission
nodes.
Original comment by LlmD...@gmail.com
on 4 Apr 2013 at 2:14
this is the config file I created:
http://pastebin.com/AX2LFmgH
And this is the perm file
http://pastebin.com/svjDpNhk
Original comment by cortiand...@gmail.com
on 4 Apr 2013 at 2:32
You haven't given any towny permission nodes in your other permission plugin
have you?
Original comment by LlmD...@gmail.com
on 4 Apr 2013 at 3:12
No, no towny-related permissions in permissionsEx
Original comment by cortiand...@gmail.com
on 4 Apr 2013 at 3:14
ok checked it out
that section of the config is for Flag war, which is different from /ta toggle
war.
You want to turn off allow_block_griefing: 'true' to stop the all-out griefing,
or use flag war if you want a more refined list of editable_materials.
Original comment by LlmD...@gmail.com
on 4 Apr 2013 at 3:18
Thank you for your answer, unfortunately we can't use the war flag mode because
it's always active (not activable/deactivable with something like "ta toggle
flag")
If I set allow_block_griefing: 'false', will the enemy be able to steal objects
from my chests? for example when the countdown is over
Original comment by cortiand...@gmail.com
on 4 Apr 2013 at 3:30
When the countdown runs out the plot belongs to the new town. Yes they will be
able to enter the chests, unless lockette is used.
Original comment by LlmD...@gmail.com
on 5 Apr 2013 at 1:45
Ok, maybe I'm st..id; but here is what happens:
- the HP countdown ends
- the message "plot x y has fallen"
but the plot is still of the previous city and attackers can't destroy or take
anything.
Am I doing womething wrong in the config?
Thank you
Original comment by cortiand...@gmail.com
on 5 Apr 2013 at 6:49
Ok, looked into it, when a plot is taken in war, the town who lost the plot
loses control of it for the duration of the war, it is given back to the town
when the war is over.
Only flag war takes ownership of the plots.
Original comment by LlmD...@gmail.com
on 6 Apr 2013 at 4:27
yes, but.. what's the thing with gain control of a plot?
technically...if block griefing is disabled, the enemy won't be able to do
anything in the conquered plot.
If block griefing is enabled, the enemy is able to destroy the plot before the
countdown reaches 0
Original comment by cortiand...@gmail.com
on 15 Apr 2013 at 4:04
Original comment by LlmD...@gmail.com
on 30 Mar 2014 at 11:03
Original issue reported on code.google.com by
cortiand...@gmail.com
on 23 Mar 2013 at 9:40