flux reports: we should get rid of the oblig ... #2087
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#2087
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?
flux reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
I would change it to default to the playername if no areaname is provided to have both options.
that's what i meant, though i didn't say it clearly :)
Big Pro: Much less explaining to do
Small Con: More likely littered areas
Small Con: More likely people using temporary areas as they go
Once we're at it, we could make an item or tool that, if placed or used, it creates a protect_this area but then vanishes afterwards or gets used up real quick. So it can't be abused, we could make it the area takes effect only after lvl/10 seconds. This item could go to the starter inventory. Opinions?
i don't think this is likely to become a real problem. some players already devastate areas even if they're unaware of protection.
a timer on how often you could use the command (once a day?) could easily prevent this.
so this would be a tool that only starting players would get, and would have, say, 4 uses? that actually sounds interesting.
then again, players might abuse this by creating a lot of alt accounts...
there's also cheapie's protector blocks, which is an iron block that creates a protection area integrated w/ the areas mod. this is one tool we use on blocky - every new player starts with one. if they can place the block, they can have an area, and they can punch the block to see the area boundaries. it requires an iron pick to break it, which prevents beginning players from picking up and moving their areas a lot...
there's also tenplus1's protector redo, which doesn't integrate w/ areas (though it works along side it), and only protects a very small volume...
i've also thought about the idea of a "powered" protection node, something like a furnace that needs to burn fuel (mese?) in order to keep the area protected, but i'm not sure such a thing is a good idea? does the person's stuff just become up-for-grabs if they don't protect it?
apparently i stole the "powered protection" node from oakenshield: #395
cf. #1945 and #1880
Fixed in
ec28e68ee8
this is live