Bla reports: [Rules] Haven alliance plot ru ... #1800
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#1800
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?
Bla reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
I guess most people get that they shouldnt use anything named "mesecon" at all no matter if its behind the mesemaker priv or not but some would probably argue.
but does that include digiline stuff? Because alot of them aren´t behind mesemaker and loosing mesemaker wont matter then. See #1682
Or pipeworks? sure those behind mesemaker probably yes but what if a couple of people make plot sized sorting stations thats gonna add up.
True. We should replace "mesecon" with a more general "machines", since we target anything active that is composed of more than one block
maybe the machine rules could be relaxed, even, particularly because mesecons_debug is present?
though i suppose part of the reason for the rule is to not get an advantage by having things loaded all the time. but is that really much of an advantage, compared to players who can just AFK 24/7?
perhaps it could be rephrased as "no automated farming of any kind" in cities? mesecons could still be used for blinking signs and the like.
The rules were made for not having even more an advantage in a busy city like Haven, and it was ruled out all machinery to not have to discuss each of those machines with plot owners.
"This is no farming machine! I needed a very longterm blinky plant and it occurred to me that a nodedetector in conjunction with the slow growth of this crops exactly covers my usecase. And the nodebreaker is only meant to reset the cycle."
Maybe only pre-approved machines in Haven etc.? They'd have to be built elsewhere and inspected before they could be installed.
Then again, who has time to inspect machines =D
EDIT, a partial summary of positions (i am falling asleep):
trying to summarize the current state of things:
If you use a blinkyplant for your blinking sign you need mesemaker to place it, non stop running blinkyplant would break mesemaker rule.
If you dont want any mesecon/digiline/pipeworks on plots I would add them all to the automation category from unified inventory and change the rule to
An "automation" group is a good idea. We could also make the whitelist feature of the yl_areas_addon accept groups