Defining "standard" NAP |
Tue, 28 February 2012 13:53 |
|
iztok | | Commander | Messages: 1206
Registered: April 2003 Location: Slovenia, Europe | |
|
Hi!
Giving the recent thread about NAP-breaking was unfortunately not the first one, it's IMO time to put it down clearly but hopefully in short terms, what in our comunity the Non-Aggresion Pact actualy means.
What we need to define is:
- teritory that is protected by NAP and how to expand it
- what actions can be taken inside and outside of that teritory
- what actions will break the NAP (maybe something around damage done compared to total player economy)
- conditions about when termination clause is to be respected and when it's immediately null and void (if we actually agree to allow this)
- obligations of sides entering the NAP (like mandatory notification of involved sides about diplomatic changes with non-involved players)
- reparations for "minor" breakings of NAP (like destroying scouts)
- ...
Anybody willing to participate?
BR, Iztok
[Updated on: Tue, 28 February 2012 13:59] Report message to a moderator
|
|
|
Re: Defining "standard" NAP |
Tue, 28 February 2012 13:58 |
|
|
I don't mind and will actually look forward to it.
For starters, things to also consider,
the minimum non-cancel able period after signing an NAP...
Disclosure of alliances with the nap parties/players
Extention of the certain basic aspects of the nap with allies
Non availability of resources to allies in case of a proxy war
If the ally is attacking the other nap party, the first nap player should inform any fleet movements on the border planets?
I know my minefields.. but I'm a chaff sweeper.
I used to curse when I got stuck in traffic... till I realised I AM traffic.Report message to a moderator
|
|
|
|
Re: Defining "standard" NAP |
Tue, 28 February 2012 14:15 |
|
|
Not wanting to rehash an old topic, so without taking names, the aggrieved party did set the correct battle orders, but as he fired on the middle party, the eventual aggressor got involved due to the stars battle engine system.
I know my minefields.. but I'm a chaff sweeper.
I used to curse when I got stuck in traffic... till I realised I AM traffic.Report message to a moderator
|
|
|
|
Re: Defining "standard" NAP |
Wed, 29 February 2012 03:29 |
|
|
Eagle of Fire wrote on Wed, 29 February 2012 07:12 | Basic NAP?
My basic NAP only cover the fact that both party agree not to attack eachother. Nothing more.
|
Seconded. And that means under any circumstances.
If the other party makes an action that is hostile to me and has not been agreed upon beforehand - even accidentally - he's broken the NAP and will face consequences thereof.
Report message to a moderator
|
|
|
Re: Defining "standard" NAP |
Wed, 29 February 2012 03:32 |
|
|
Consequences?
What's the max one can do?
Call him names and attack him.
However the point of the nap is that one doesn't require to have a full alert defence fleet. It's in this situation that the other party takes advantage and decides to "tweak/push" the nap.
They can take the aggressive action in game while you are not fully prepared to block their actions and to deflect RL name calling, go into legalese and clause lawyering of the nap.
Edit - split sentence into two.
[Updated on: Wed, 29 February 2012 11:46]
I know my minefields.. but I'm a chaff sweeper.
I used to curse when I got stuck in traffic... till I realised I AM traffic.Report message to a moderator
|
|
|
|
|
|