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.

Sign up for GitHub

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

Jump to bottom

Corridor Variation Selector #1995

Open
TeamSpen210 opened this issue Nov 17, 2023 · 0 comments
Open

Corridor Variation Selector #1995

TeamSpen210 opened this issue Nov 17, 2023 · 0 comments
Labels
Done in next release This has been addressed in the next release New Feature New feature of the app or compiler Priority: Low This issue isn't very important

Comments

@TeamSpen210
Copy link
Member

TeamSpen210 commented Nov 17, 2023 •
edited

Description of the feature

For each corridor, add the ability to define dropdowns, which allow picking from fixed options to set a fixup. These would either be defined individually for each corridor, or defined globally for a style + combination of types. Optiomally there'd be an additional choice in the dropdown to randomise the value from the map seed.

Why should this be implemented

This would allow for selecting more minor changes to corridors - things like light temperature, direction, etc. Global options are intended for elevators and things like that.
@TeamSpen210 TeamSpen210 added New Feature New feature of the app or compiler Priority: Low This issue isn't very important labels Nov 17, 2023
@TeamSpen210 TeamSpen210 mentioned this issue Nov 21, 2023
Closed
@TeamSpen210 TeamSpen210 added the Done in next release This has been addressed in the next release label May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Done in next release This has been addressed in the next release New Feature New feature of the app or compiler Priority: Low This issue isn't very important
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@TeamSpen210