Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better document parameters of Programmer puzzle pieces #1353

Open
bartico6 opened this issue Oct 3, 2024 · 0 comments
Open

Better document parameters of Programmer puzzle pieces #1353

bartico6 opened this issue Oct 3, 2024 · 0 comments

Comments

@bartico6
Copy link

bartico6 commented Oct 3, 2024

Describe the feature

What each parameter/side does in puzzles isn't immediately obvious, neither is it well explained in the Patchouli book provided. Same applies to special variables like $drone_pos. Update: no it doesn't apply, it's in the book and I missed it.
Take the following example "wait for targets in safezone" snippet of a drone program implementing base defense:
image
The fact that p1 is top-right, and p2 is mid-right isn't immediately obvious - as a similar operation defining two corners using a coordinate operator looks like this
image
Similarly, which path the program takes in conditions (on eval true it takes label on the right, on eval false it takes label on the left, if one isn't present falls through to block below) also isn't immediately obvious, and warnings are not raised for having blocks attached to the bottom of a conditional with both true/false labels filled, like this:
image
This should absolutely raise a warning, if not hard error - as it is "unreachable code".

Reasons why it should be considered

Programming drones in PNC is unclear and confusing, even to people with a programming background, as trying to implement something interesting using the programmer requires you to trial/error with the programming puzzles a lot, check mod source code, or look it up online. Functionality of blocks and parameters should be in-built into the programmer UI - the tooltip of the puzzle should tell you what each parameter is and does.

This would make programming drones accessible to more players without watering it down ( especially those who are otherwise talented, but unwilling to seek out source of the mod just to understand the puzzles, if they can just use a different machine in their modpack to achieve the same result ;-) )

Additional details

No response

@bartico6 bartico6 changed the title Better document parameters of Programmer puzzle pieces as well as meta variables Better document parameters of Programmer puzzle pieces Oct 4, 2024
desht added a commit that referenced this issue Oct 13, 2024
It is now a programmer error to have this situation

#1353
desht added a commit that referenced this issue Oct 17, 2024
Security upgrade was checked before air handler was ready to be
notified.

Move all upgrade init logic to onLoad(), don't call getUpgrades() from
 loadAdditional() anymore; leads to onUpgradesChanged() called too early.

#1353
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant