Freebie reports: Mese machines should be able t ... #3417
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
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#3417
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?
Freebie reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
Machines that are not in active mapblocks should be turned off anyways. There are plenty of mechanics to have an off switch, among them a simply lever. There is even a "player online" detector.
Techniques like this could be displayed in a mesecon tutorial
also, lag due to mesecons is unlkely, mesecons_debug is over-zealous, particularly when there's only machines working in one place.
Freebie is knowing that, but there are certainly many other good possibilities, especially smaller or vertical circuits, which can be easily integrated into existing machines.
Yes, I read somewhere that someone wanted to build. Who else was that?
Yes, but sometimes even a forgotten preasure plate can be too much...
What mechanic would you suggest? Do you have something specific in mind already?
It can't get smaller than a single block, right?
There were at least four separate attempts, none of which came to fruitition. maybe we should change the mesemaker priv exam to "... and build us one demo-circuit which is not yet in the mese-tutorial" ?
pressure plates do not know who owns them, so we can't disable them along the player online status. Forgotten pressure plates need to be dealt with like any other forgotten thing: Found and ... done something to them.
I am not a pro on this, but to organize it, should be worth a fifth attempt?
Or they have to give you the right to copy every machine into that tutorial?
Its easy to cut a cable. But if you want to have things like this in the smallest way, how to build this comfort version in 2x2x2?
I saw the one upie started and it´s hard to decide what to display especially for YL which doesn't really want players to use automation afaik.
Also the limits YL added to mesecons/digilines aren't really documented except in code commits which aren't accessible by everyone so it's trial & error to find them and mesecon/digiline items are pretty costly on YL too.
They would need mesemaker priv first to build that demo-circuit and someone remembering to remove that priv after a certain time or if they failed 😉
There are also not that many unique circuits to show someone in a tutorial how mesecons/digilines work, so it would get hard quickly to find something really new.
Also if pipeworks gets replaced at some point you also need someone to "fix" all those demos.
In general the current mesemaker test has it flaws but by not providing help with mesecons/digilines it limits pretty good how many people(aka future cause of lag) apply for mesemaker because you really have to spend time and gather the information yourself instead of just building a variation of a demo you saw in the tutorial.