+- Discovery Gaming Community (https://discoverygc.com/forums)
+-- Forum: Discovery General (https://discoverygc.com/forums/forumdisplay.php?fid=3)
+--- Forum: News and Announcements (https://discoverygc.com/forums/forumdisplay.php?fid=13)
+--- Thread: Developer Notice: Cloak Changes Trial Phase (/showthread.php?tid=118261)
RE: Developer Notice: Cloak Changes Trial Phase - An'shur - 07-23-2014
So, lets prepare couple of /setmsgs for my Nomad. (No, I am not belonging to people /l1 > fire)
Every person loving decloaking and instakilling will prepare /setmsgs too.
Really no problem at all
RE: Developer Notice: Cloak Changes Trial Phase - Oldum - 07-23-2014
Oh god .. this announcement basically killed half of my ideas I was planning to se cloak for ... Oh well, back to the drawing board ... and before anyone yells at me, no I wasn't planning on insta-killing people upon uncloaking behind them.
RE: Developer Notice: Cloak Changes Trial Phase - Alhimik - 07-23-2014
Oh my Lord...
This of cause good idea, but maybe you add some equipment who can help detect cloacked ships?
~Alhimik
RE: Developer Notice: Cloak Changes Trial Phase - Alley - 07-23-2014
(07-23-2014, 11:58 AM)Alhimik Wrote: Oh my Lord...
This of cause good idea, but maybe you add some equipment who can help detect cloacked ships?
~Alhimik
We're thinking about it, it's the technical side of the things that's a bit troublesome right now.
RE: Developer Notice: Cloak Changes Trial Phase - Knjaz - 07-23-2014
Not sure on the system chat disabling, though. It would end up with massive use of /setmsg for surprise attack.
And yes, before you disable /setmsg again: (Since I totally see it coming, knowing local community and how "balance" is being worked around in here, with helluva lot of side-effects not being taken into account whatsoever).
You're with 4-5 cloaked heavy battleships. Those that usually need to get close to be able to win the fight, you know how Freelancer/Disco capship combat mechanics work.
Behind 5 uncloaked enemy medium/light battleships already engaged in combat.
How do you see it? You uncloak, and either type a long engagement notice while enemy regroups, thus fully losign the surprise effect, or wait until enemy understands what's going on and will focus fire on one of your ships without engagement notice (since he's in combat already), so you could fire back - thus losing a surprise effect again.
And the point of using cloak under such conditions would be... to just get close?
Once again, just typing it here in advance, to save time in future.
P.S. Totally support the disabling of Local chat for cloaked ships, though.
RE: Developer Notice: Cloak Changes Trial Phase - Alhimik - 07-23-2014
I have many ideas to upgrade Disco, now I work to my client with changed music and graphic, I think add another group of starsheres to Gallia, maybe If you interested I give to dev's this client later
P.S: Maybe you can say, how to add it(starspheres) and edit gallia INI files.
~Alhimik
RE: Developer Notice: Cloak Changes Trial Phase - Alley - 07-23-2014
(07-23-2014, 12:14 PM)Knjaz Wrote: Not sure on the system chat disabling, though. It would end up with massive use of /setmsg for surprise attack.
And yes, before you disable /setmsg again: (Since I totally see it coming, knowing local community and how "balance" is being worked around in here, with helluva lot of side-effects not being taken into account whatsoever).
You're with 5 cloaked battleships.
Behind 4 uncloaked enemy battleships already engaged in combat.
How do you see it? You uncloak, and either type a long engagement notice while enemy regroups, thus fully losign the surprise effect, or wait until enemy understands what's going on and will focus fire on one of your ships without engagement notice (since he's in combat already), so you could fire back - thus losing a surprise effect again.
And the point of using cloak under such conditions would be...
Once again, just typing it here in advance, to save time in future.
I don't see why setmsg would be disabled, it is not an issue here. I think what people were mostly bothered about were cloaked trolls and people sending the engagement notice a few seconds BEFORE decloaking, which is borderline abuse IMO. No more wtfpwning.
As it's said in the first post, it's a two weeks trial, use these two weeks to observe, try it out and comment to make a difference.
RE: Developer Notice: Cloak Changes Trial Phase - Zayne Carrick - 07-23-2014
Quote:We're thinking about it, it's the technical side of the things that's a bit troublesome right now.Maybe ship can stay cloaked, but it'll be available on scanner if you have anti-cloak? So only the ship with anti-cloak will be able to target it.
(Dunno, but I think it's easier to code than complete cloak neutralizer)
RE: Developer Notice: Cloak Changes Trial Phase - Knjaz - 07-23-2014
(07-23-2014, 12:24 PM)Alley Wrote: I don't see why setmsg would be disabled, it is not an issue here. I think what people were mostly bothered about were cloaked trolls and people sending the engagement notice a few seconds BEFORE decloaking, which is borderline abuse IMO. No more wtfpwning.
As it's said in the first post, it's a two weeks trial, use these two weeks to observe, try it out and comment to make a difference.
No more wtfpwning??!!!
But that's exactly what your decision is bringing!
I would understand if you've done it in order to prevent cloaked trolling, where you fly around someone and troll him in local. Wasn't that the whole purpose of this change?
K, I'll try to describe it in a more detailed way.
Step 1: Move light bomber/cruiser craft into enemy fleet formation. Make them busy.
Step 2: Initiate cloak sequences for battleship fleet.
Step 3: Move cloaked BS behind the enemy. In the process, Battleships (while cloaked) give preliminary roleplay in system chat to show their intentions.
Step 4: Battleships get behind enemy fleet, give out actual engagement notices in local and uncloak.
Step 3 to 4 under new mechanics:, uncloak and instantly do a /setmsg engagement notice.
Result: A massive increase in uncloak-setmsg-open fire use. >>>> Result: Disabled setmessages once again.
I'm sorry for the ****ty formatting, just lacking time and trying to show several points that are rather obvious for all parties involved in cloak use, on both ends (attacked and defenders). Which also brings me back to my old question on how often DevTeam really plays - for example, when did DevTeam members involved in the brainstorming of this decision participated in large scale fleet combat on cloaked battleships, to have the full understanding on how various components of the game content involved in those scenarios interact with each other?
RE: Developer Notice: Cloak Changes Trial Phase - Sath - 07-23-2014
(07-23-2014, 12:53 PM)Knjaz Wrote: Step 3 to 4 under new mechanics:, uncloak and instantly do a /setmsg engagement notice.
Result: A massive increase in uncloak-setmsg-open fire use. >>>> Result: Disabled setmessages once again.
Quote:3.1 An attack is any hostile action that drains shields to less than 50%. Saying "Engaging" is not sufficient and aggressors are not allowed to destroy a ship before allowing sufficient time to respond. If a player is attacked he has the right to defend himself regardless of who is attacking. Trading nanobots, shieldbatteries or other ammo and equipment during a fight is also considered taking an active role in the engagement.
What you just said, is sanctionable. btw, this solves a lot of problems, like cloaked BS sneaking up and then suddenly uncloaking, killing you.
Since, before this change, people typed in engagement notices, waited for some time while still sneaking behind, and after ample amount of time, instakill you. Which, as Alley said, is borderline abuse.