(05-16-2013, 08:45 PM)belarusich Wrote: Now it is even better, i can fastly type "engage" and kill enemy!!
I so hope you are sarcastic. I honestly do. If not, the few that reside in the same country you do should come and kick a certain someone for him/her ruining the beliefs shared by a lot of folks on the internets about the typical behaviour generally portrayed.
Please, proof me wrong. Say you're sarcastic and don't make me drop my last straw of hope I have.
When it comes to the topic, I've noticed a rather large increase (or rather absence) of people actually saying any greetings, especially amongst traders. Since it got removed space got a bit more silent, and I know, in the vast nothingness of space there is no sound, but the airwaves are dead as can be. Tedious. Good job on removing this and not looking for potential other ideas that could lessen/eliminate the /1 /2 insta-pew folks. Honestly. Discovery RP 24/7. Yeah. Right.
(05-16-2013, 02:59 PM)why_so_serious Wrote: An actually pretty easy solution would be to drop the energy after you use the setmsg command.
That would render its use to call targets in group chat completely useless. Or render you completely useless in order to call a target.
awww pls. How do you call targets right now? Anyway saying like 4 or 5 letters of the next target is more than enough and every should be able to do that.
Quote:How about to give it back, and simply -forbid- to use it for engaging notices?
No, that would be bad. But you could set a time limit for this command.
Quote:Now it is even better, i can fastly type "engage" and kill enemy!!
How often i have heard these messages already:
Admins, do you think the removal of the commands will avoid such kind of engagement notices? NO! it gets worse. You only hurt the loyal roleplayers.
Quote:In result, it is a loss of atmosphere, which is very bad for the future of an nearly 10 years old game.
I agree with that.
Many people, (Like me), built up and improved their RP-Atmosphere with this /setmsg commands. Kill this function... And you will kill another part of discovery with it.
And what i want to say is, you should use this commands only in special situations.
In events or if you don't have enough time to write one, for example.
This is the msg-list of my char, RNC-Schiller.
---Engagement notices---
0 -|--- Standard Emergency call - Location #c ---|-
1 Feindkontakt!... Code red!... Shields at maximum, weapons online!
2 Ziel erfasst... fire at #t
---Special RP notices---
3 "Empty for special-purposes" <-- I have used this slots for a deeper RP adventure, like liberty raids, events or something like that.
4 "Empty for special-purposes"
5 "Empty for special-purposes"
6 "Empty for special-purposes"
---Dead notices---
7 Decompression at section 7!... Hit on the supply line!... We lose fuel!... Reactor energy fluctuates!
8 We lose coolant and the reactor temperature is critical!... Contact with the engine room lost!... System overheat!
9 Hit on the reactor!... We lose the insulation case!... OH MEIN GOTT!... KERNBRUCH!
At the moment i am really bored. I miss this function... :/
I haven't used it in a while, but I do miss the possibilities it offered. Keeping overwatch on a trade embargos was simple with well typed /l messages where I could use #t.
i.e.
/l1 - "Wicks: Hail there, #t, cut your engines and stand by for inspection."
/l2 - "Wicks: #t, cut engines immediately or be fired upon."
/l3 - "Wicks: Alright #t, you look clear. Have a safe journey."
/l4 - "Wicks: #t, for violation of Liberty Law, your vessel is subject to summary destruction. Moving to engage."
Really handy in situations where you're dealing with a lot of vessels at once. And I dare anyone to tell me that the above isn't "proper RP". It does get weird when the names are weird, but at least it's clear who you're taking to when you use #t.
EDIT:
I of course use actual typed out sentences to resolve anything of interest in between, but at least I'm not wasting time trying to make sure the right person understands I'm talking to them while I handle three other vessels at the same time.
Quote:How about to give it back, and simply -forbid- to use it for engaging notices?
No, that would be bad. But you could set a time limit for this command.
Quote:Now it is even better, i can fastly type "engage" and kill enemy!!
How often i have heard these messages already:
Admins, do you think the removal of the commands will avoid such kind of engagement notices? NO! it gets worse. You only hurt the loyal roleplayers.
Quote:In result, it is a loss of atmosphere, which is very bad for the future of an nearly 10 years old game.
I agree with that.
Many people, (Like me), built up and improved their RP-Atmosphere with this /setmsg commands. Kill this function... And you will kill another part of discovery with it.
And what i want to say is, you should use this commands only in special situations.
In events or if you don't have enough time to write one, for example.
This is the msg-list of my char, RNC-Schiller.
---Engagement notices---
0 -|--- Standard Emergency call - Location #c ---|-
1 Feindkontakt!... Code red!... Shields at maximum, weapons online!
2 Ziel erfasst... fire at #t
---Special RP notices---
3 "Empty for special-purposes" <-- I have used this slots for a deeper RP adventure, like liberty raids, events or something like that.
4 "Empty for special-purposes"
5 "Empty for special-purposes"
6 "Empty for special-purposes"
---Dead notices---
7 Decompression at section 7!... Hit on the supply line!... We lose fuel!... Reactor energy fluctuates!
8 We lose coolant and the reactor temperature is critical!... Contact with the engine room lost!... System overheat!
9 Hit on the reactor!... We lose the insulation case!... OH MEIN GOTT!... KERNBRUCH!
At the moment i am really bored. I miss this function... :/
Sanction them, they'll learn to RP, np np.
You would rather them just being able to attack you sooner, in this case, by doing /l1-pew, instead of type a message, type another message, pew? Np np, that's what Connecticut is for.