Ok, this is to the developer of this game.

I know how you can severly hinder the ability of griefers while at the same time not ruining game play for others.

Here is my idea: Add a timed counter that keeps track of the number of friendly blocks you destroy withing 1 minute. So that if a teammate destroys (lets say) 20 friendly blocks within 1minute; auto kick their griefing ass!

Also another possible change would be to make blocks that YOUR team laid take longer to destroy if they have been on the map for more that 5minutes; say 9 pick hits instead of 3 & also disable spade use on friendly blocks/ structures.

I think that these simple changes would inhibit griefing severely. I know some c++ and I am sure this would be a very easy change to make to the code of the game.

If you like some or all of these ideas please reply and keep this thread alive! - this is for the good of the game. I am sick of people taking seconds to destroy what can take hours to make!

no, then you cant get rid of the stupid shit that gets in the way eg. random giant penises and rogue walls.

to stop griefing you shoot the duece who continues to break your stuff.

Chinopwned, I guess u read my thread a little to late, I thought the same thing and figured a timer would be in order, so i edited my post; if a structure is out for more than 5min THEN it becomes stronger to teammates

That still isn't a good idea. What this will add is a huge amount of overhead and will be likely to bog down the host. Currently all that a server host needs to do is calculate where each player is (3 numbers), the direction they are facing and whether or not a shot hits. Ammo, health calculation, movement and block breaking is all accomplished client side (thus the people who "hack" these aspects). Because of this my factory made 5 year old Dell laptop can host a 32 player game without lag or crashing and still run Morrowind at a sane speed. By adding the need for a hosting computer to calculate some hundreds of 5 minute timers (especially during the early game) you severely limit the amount of dedicated server hosts who are using their computers for other things during the time when they are hosting.

You can code this yourself using pyspades once I expose the block destroying/adding API. Link: http://code.google.com/p/pyspades/

Griefers will find their ways..
Although, as mat^2 says, you may be able to code this using pyspades, I think that there's one solution already built into pyspades: clear votekicking.
Pyspades uses server messages in chat to say when a votekick has been initiated, you can add a reason to the votekicking (using '/votekick #ID <reason>'), and then it updates as more people vote.
It is as good as we can get currently, until bcool gets around to creating a full votekicking UI.

We are discussing how to tackle the griefing issue in #AoS ( http://www.aceofspadeswiki.com/index.php?title=IRC ) if anyone's interested in joining us.

But the best solution to griefing is: only build things that maintained easily and replaced quickly. It's a war game, with sandbox elements. Build things in good positions to aid defense. 90% of the big forts I see don't actually get use for defense - they are just added to and made pretty by a builder in a world of their own.