Sokomine reports: remove area_upvote command. on ... #6071
Labels
No Label
1. kind/balancing
1. kind/breaking
1. kind/bug
1. kind/construction
1. kind/documentation
1. kind/enhancement
1. kind/griefing
1. kind/invalid
1. kind/meme
1. kind/node limit
1. kind/other
1. kind/protocol
2. prio/controversial
2. prio/critical
2. prio/elevated
2. prio/good first issue
2. prio/interesting
2. prio/low
3. source/art
3. source/client
3. source/engine
3. source/ingame
3. source/integration
3. source/lag
3. source/license
3. source/mod upstream
3. source/unknown
3. source/website
4. step/approved
4. step/at work
4. step/blocked
4. step/discussion
4. step/help wanted
4. step/needs confirmation
4. step/partially fixed
4. step/question
4. step/ready to deploy
4. step/ready to QA test
4. step/want approval
5. result/cannot reproduce
5. result/duplicate
5. result/fixed
5. result/maybe
5. result/wontfix
ugh/petz
ugh/QA main
ugh/QA NOK
ugh/QA OK
No Milestone
No project
No Assignees
7 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#6071
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Sokomine reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
Having only one area to be upvoted OR downvoted per week makes one think a bit before adding a +1 or -1 to an area. Also, it remove at least some abuse potential.
sokomine and i agreed that limiting it to once per week makes it too easily forgettable. i can rarely use it, and so i rarely remember to use it. whenever i think about the command, i realize i wished i used it more.
maybe only limit it to once per 24 hours, and also limit a player's ability to vote on their own area (including alts)? what other exploits are there?
The amount of areas worthy upvoting does in no way correlate to that once-per-week interval. At least not for me. When I'm exploring, I'm far more likely to find new areas with something worth upvoting. Shall I stop and give up at the first worthy area? And then come back to the spot next week and continue exploring from there? That just doesn't work. Once per week usually isn't even enough for the great contributions to the BotM award.
Perhaps keep downvote to the weekly interval as that ought to be used only in rare occasions. In general, we do have the /bug command to report areas that really need removal/fixing.
A global list of who upvoted which area might also be helpful. This might inform players of areas worth visiting of which they havn't even heard before. Such a list can also help to limit upvotes to one upvote per player and area.
And if the game stores who upvoted where it's also possible to revoke upvotes from a certain player if alts get abused for that.
Wouldn't work backwards for old votes but wouldn't be too much work for new upvotes.
If this is being tweaked, please also deal with Issue #4904
I supported Sokomine's proposal: one vote per plot and player (but possible in both directions) and that's it. Or you can change this one vote again and again, as with the bailiff vote.
However, all these votes are quite inaccurate in terms of area. If, like Sokomine, you want to be able to vote for each individual building, then this requires that there is exactly one corresponding area for each building. You can certainly prepare for this if you are interested in it as a builder. But most areas will continue to contain more than just one building, especially in the province. Entire cities sometimes consist of only one city area.
The main disadvantage of the current system, however, is its possible irrational use. I had criticized the content of a player's building in detail and later downvoted it with an announcement. Immediately my plot in Haven was downvoted, unfortunately without any concrete hints, but simply as an act of revenge. Ok, I then organized an upvote and so it is now at 0.
So you can be glad that far less than 1 percent of players know these commands and rarely use them, and so far I know of only one sprawling campaign in this way. Therefore, there is not only ignorance in the commands, but widespread disinterest.
Therefore, I think it would be much better if there were another or complementary form of evaluation instead of anonymous voting.
Proven construction experts (e.g. those who were among the top three in the Botm three times) were asked to evaluate structures at the request of the builder or a mayor. To do this, they can develop their own rating scale. And as a result, there should also be badges (yes, yes node limit, but it would be worth it). And a few words or examples of what could be changed.
BTW, at the moment the Botm leads to some particularly beautiful buildings of a still much too small circle of builders, but in the area this does not automatically lead to a higher construction level.
Hmm. More buildings in one area may certainly pose a problem. Especially to players who are less familar with the technology behind it. That problem exists with the current voting system as well. Getting the right target area isn't easy.
Seems that area downvote is the larger problem. I don't think it's good for players when their area - even if it deserves it - gets downvoted. Not in a situation as Boot described - when giving detailled feedback and afterwards downvoting (that's great if a player receives so much feedback!) - but when it's excessively used or as a form of revenge.
I'd really love to have a review system. Not as restricted as Boot suggested but not open to the next best alt that managed to type a username in either. Something inbetween. Player level may be an indicator, but honestly it does measure something completely diffrent. Rather a builder's club.
A public list of recent upvotes and a list of areas showing how many upvotes they got might help players find places that are worth visiting and which they havn't found on their own yet. It'd also be not too complex to implement.
Maybe remove upvote and downvote, and add an area_suggest command that allows you to give suggestions.
For this reason I've tried to establish Upvote Sunday as an unofficial tradition.
I usually forget the date, and it's difficult to keep track of what building you've liked the most among the ones you've visited during the week.
But I think I've managed to raise awareness of the existence of this command to a handful of people at least.