Anuken / Mindustry-Suggestions

Repository for Mindustry suggestions and feedback
130 stars 58 forks source link

Unit/Turret Kill Counter (Track Turrets / Units Efficiency) #2048

Closed G0nTar closed 3 years ago

G0nTar commented 3 years ago

Describe the content or mechanics you are proposing.

-Basically, adding a track of individual Turrets/Units kill count or damage dealt, to track how efficient they are on the battlefield and give better feedback to players and "creating a sort of bond" to some of their structures n' units

Describe how you think this content will improve the game. If you're proposing new content, mention how it may add more gameplay options or how it will fill a new niche.

-It would make players engage in a deeper way with their units n' turrets, being able to know good a turret or unit is doing.

-It can help to improve new players n' veterans defensive and offensive strategies, since you have more data and a better understanding of how well your military units/turrets are doing.

-Plus you can feel more attached to certain units or turrets when you notice how good they're performing, giving players a warm feeling of: "Look how many bad guys you helped me take down!! How's a good boy?! You are!"

That is all.

Before making this issue, place an X in the boxes below to confirm that you have acknowledged them. Failure to do so may result in your request being closed automatically.

    • [x] I have done a quick search in the list of suggestions to make sure this has not been suggested yet.
    • [x] I have checked the Trello to make sure my suggestion isn't planned or implemented in a development version.
    • [x] I am familiar with all the content already in the game or have glanced at the wiki to make sure my suggestion doesn't exist in the game yet.
    • [x] I have read README.md to make sure my idea is not listed under the "A few things you shouldn't suggest" category.
itcannotbe commented 3 years ago

Please edit you suggestion. All I see is the template and the title, otherwise it's empty.

G0nTar commented 3 years ago

Please edit you suggestion. All I see is the template and the title, otherwise it's empty.

i was on it, accidentally sent the template half-finished, and i jumped right away to fill it when i noticed the miss-click :)

Thanks for noticing it that fast tho <3

itcannotbe commented 3 years ago

Need to exclude online and custom games from stats gathering.

Otherwise inflating numbers is easy.

G0nTar commented 3 years ago

Need to exclude online and custom games from stats gathering.

Otherwise inflating numbers is easy.

So? What's your point, on campaign or even Multiplayer, i see no problem on any showing you a killcount, if your concern is network overload, you can keep it Local to the client, i see no issues yet.

itcannotbe commented 3 years ago

Well this can get implemented to seperate online activity too. XD

G0nTar commented 3 years ago

And it's not a complex and over complicated feature. It would be a day or 2 of creating the Script and testing it, adding a label n' integer attached to it on the GUI, and if you don't want to send it over the network to all the clients, then that's what has to be kind of done from a programmer's Perspective.

i don't do javascript otherwise i would give it a try to make it a mod first, get some feedback and give anuken a hand with the code since he's already doing so much work

Bohaska commented 3 years ago

Need to exclude online and custom games from stats gathering.

Otherwise inflating numbers is easy.

I think he meant like using this feature to see how efficient the turrets are, not using this feature like a high score sort of thing

itcannotbe commented 3 years ago

Need to exclude online and custom games from stats gathering. Otherwise inflating numbers is easy.

I think he meant like using this feature to see how efficient the turrets are, not using this feature like a high score sort of thing

I'm pretty sure people will use this to brag about something.

joshuaptfan commented 3 years ago

It would just be an additional "Damage dealt: X" in the hover info. (I suggest tracking damage dealt instead of kills, as it would provide a more accurate picture of each turret's effectiveness.)

No long term stat tracking for all turrets of this type is necessary. This would help players optimize their defenses by relocating turrets that have dealt no damage.

marky0470 commented 3 years ago

So this would be a new variable for the sensor to get like @damageDealt or @unitsKilled?

Jammo2000 commented 3 years ago

I agree with Joshua, damage dealt is a much better measure. Otherwise foreshadows (which get few kills but good damage) would be on a different scale than crowd control like ripples.

SheepCommander commented 3 years ago

Ye damage dealt

G0nTar commented 3 years ago

Need to exclude online and custom games from stats gathering. Otherwise inflating numbers is easy.

I think he meant like using this feature to see how efficient the turrets are, not using this feature like a high score sort of thing

I'm pretty sure people will use this to brag about something.

What is this comment? Like, what??? for real..

Idk why guessing that maybe someone may brag about anything would have something to do with this suggestion at all.

It's like saying game trophies are bad because people can brag of having those too.

There's even a high score feature in the game already! I see no one bragging about their high score on any map, and even if someone did it's not even related to the game itself whatever people do with their time

Either way, this feature has nothing to do with highscores, or anything you can brag about, it seems you didn't even take a minute to properly read the suggestion at all.

It's purpose (as some gentlemen pointed you out already) is to have a better feedback of turrets / units effectiveness depending on positioning / ammo / buffs etc..

By just adding 1 feature.

Tracking how they are performing...

Like their dmg output, etc

github-actions[bot] commented 3 years ago

This suggestion is now stale, and will be automatically closed.