Player Features and Ideas Discussion

Bump...

Love this thread!

Dear ISDs:

Please just sticky this thread already. It can only be beneficial.

Signed,
Features & Ideas Posters

Rumpy Bumpy

EDIT:



And I laughed at you both laughing :-)

Bump

Would be easier on everyone if this was sticky (hint hint)

Damn you for beating me to the bump! Here I was trying to do good, sigh. Guess that is what I get for taking a long time to post.

Since you also want to keep the legion contained in one place allow me to add to this cesspool from here.

Please keep in mind that the suggestions mentioned below are work in progress and should be wieved as a whole. For that reason I will for now only give a very basic presentation.

TL:DR at bottom of the post.

Hate it, dislike it, be neutral about it. It don't really matter to me at this stage and If you want to flame it, fine, but please be constructive about it. Have questions about it or want me to elaborate then respond and I will do it to the best of my abilities.


Changes to the chat.

Local should be set to only show players in your alliance, chatting is also filtered to display the chatting of your alliance only.
New channel introduced for constellation. Like npc corp chat will show number of players in the chat (constellation), friend and foe, but will not show playerportrait unless player has typed in it.

Posibilities.

Local will show number of players in the system. This in regards to the gates tracking you traveling to and from
the system.

Ships entering or leaving through wormhole accesspoints will not be added to or subdracted from the number of people in the system, since they did not enter or leave via a gate.



Possible current change for cloak.

Spec ops cloak will, during 10 seconds after going out of gate cloak, not reveal player on grid.

Tech 2 cloak will, during 6 seconds after going out of gate cloak, not reveal player on grid.


Future possible cloak changes.

spec ops cloak. 2 stage system. Passive and active cloaking. Passive cloaking remove player-position and
information on grid. Active cloaking hides ship aswell.

tech 2 cloak. 2 stage system. Passive and active cloaking. passive cloaking hides player-postition and information on grid. Active cloaking hides ship for 60 min. (+15 mins per level in cloaking)

tech 1 cloak. 2 stage system. Passive and active cloaking. Passive cloaking hides player position on grid. Active cloaking hides ship for 30 min (+7min30sek. per level in cloaking)

Change I would like to see for spec ops class ships (cosmetic). Ventet thrusters.



Counter.

scanner module.
Maybe high or mid slot.

Gives dscan ability to pick up cloak signature on grid. Will show ship type if cloaked ship is within scan radius. 10 sek cooldown between each scan (-1 sek per level in scanning) and a 20 sek calibration delay (-2 sek per level in scanning)

Possible future counter.

Ship class with spesific scanning role, or a tech 2 variant of the module, adding further reductions in the time needed for calibration and/or scanning cooldown.

Defensive deployable. Needs launcher.

A deployable that can detect a hostile lock and will then begin a countermeasure to "steal" the first volley aimed at the target the deployable belongs too. The deployable WILL be destroyed after the first volley no matter the amount of damage projected. The deploable can not be picked up or reused, and only one can be used per player at a time. The deployable will be visible on grid for 2 minutes after launch. After that time it will activate a cloak of its own.

The defensive deployable can stay active for 14 min. (+4 min. per level in the deployable skill) After it has expired a new will have to be launched

TL:DR
A series of suggestions to change the staus quo. I would like it if you read the whole thing.

Thank you for the feedback.

I read through your suggestions despite what you, and others, may think and I can agree to the notion that coming up with a good balance is... dificult. Having cloaked, "poss'ed" and docked pilots prevented from seeing whats in the chat in return for their respective invulnerables (or states) is interresting and fair, but I wonder about the coding of it.

Having a ship that can actively hunt cloakies would be lots of fun, and may add a mutch neede ship role. I have an idea or two about sutch a ship myself and I may, or may not present that too, depending on feedback here. I don't want to yet, since they are very easy to get wrong, and I want to have a good grasp on what can be considered good balance.

I personally want to do away with the local as a potential for intel altogether and keep it as an alliance/corp chat, the possible suggestions are depending on feedback, and are subject to change.

With these current suggestions no one will benefit from local at all. While giving cloaks a bypass through gate camps. And have an on grid defense for spec ops ships. Please correct me if im wrong, but only spec ops ships, with their cloak module can warp cloaked after all. And I feel these might be the easiest to code. I don't mind if you disect my suggestions and tell me exactly why you think I am wrong, or why its a bad balance, and I do take it into account.

I may try to defend it though

An addition to the deployable aswell. Incase people desides to get picky. It only repsonds to the agression of ships fitted with a cloak.

personally, i will give cloak device a timer like the mining laser. It takes a long time to cycle but you can cancel it at any moment. However, you can't auto repeat it. A further nerf will be having a de-cloak cool down timer.

Or just remove the cloaky dude from the local channel just joking

The current claoking mechanic is the WORST game mechanic in the game. It singlehandedly has resulted in the massive ratio of high sec residents to null residents.

IMO, this should be CCP's #1 priority!


The very large number of threads on the topic only demonstrates the importance of this.


As for remove local, few changes I can think of would have such a drastic and immediate crash in both the number of subscribed accounts and the total level of player activity.