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

Separate Build for TRX and Custom Levels? #1846

Closed
Raildex opened this issue Nov 7, 2024 · 1 comment · Fixed by #1854
Closed

Separate Build for TRX and Custom Levels? #1846

Raildex opened this issue Nov 7, 2024 · 1 comment · Fixed by #1854
Assignees
@lahm86
Labels
Feature New functionality TR1 TR2

Comments

@Raildex
Copy link

Raildex commented Nov 7, 2024

As a level designer, I have a clear vision of how my level should be played and do not want some options of the global ConfigTool to be applied to my level.

Would it be possible to provide two different binaries? One for TR1X - TR1 Community edition and one specifically for custom levels where all the config is read from gameflow.json?
@rr-
Copy link
Collaborator

rr- commented Nov 7, 2024

I understand your perspective as a level designer and the importance of maintaining your vision. While offering different binaries isn't feasible for us, I think we could add a feature to freeze certain options in the gameflow. This might allow builders to restrict changes to things like water color or rendering distances. Could you let us know which specific options are causing the most difficulty for you?

In the meantime, a possible solution could be to include a predefined config with your level and omit the config tool.

@aredfan aredfan added the TR1 label Nov 8, 2024
@lahm86 lahm86 self-assigned this Nov 9, 2024
@lahm86 lahm86 added the TR2 label Nov 9, 2024
@lahm86 lahm86 moved this to In progress in TRX Dev tracker Nov 9, 2024
lahm86 added a commit to lahm86/TRX that referenced this issue Nov 9, 2024
@lahm86
libtrx/config: support enforced config settings
8713aae 
This allows an enforced object to be defined in the config file, within
which any regular config setting can be defined, and the values from
here will be enforced in the game.

Enforced settings are not shown in the config tool, but will be
preserved on write.

Resolves LostArtefacts#1846.
@lahm86 lahm86 added the Feature New functionality label Nov 9, 2024
@lahm86 lahm86 mentioned this issue Nov 9, 2024
Merged
2 tasks
@lahm86 lahm86 moved this from In progress to In review in TRX Dev tracker Nov 9, 2024
lahm86 added a commit to lahm86/TRX that referenced this issue Nov 10, 2024
@lahm86
libtrx/config: support enforced config settings
992957f 
This allows an enforced object to be defined in the config file, within
which any regular config setting can be defined, and the values from
here will be enforced in the game.

Enforced settings are not shown in the config tool, but will be
preserved on write.

Resolves LostArtefacts#1846.
lahm86 added a commit to lahm86/TRX that referenced this issue Nov 10, 2024
@lahm86
libtrx/config: support enforced config settings
1210c2e 
This allows an enforced object to be defined in the config file, within
which any regular config setting can be defined, and the values from
here will be enforced in the game.

Enforced settings are not shown in the config tool, but will be
preserved on write.

Resolves LostArtefacts#1846.
@lahm86 lahm86 closed this as completed in 3ca5456 Nov 10, 2024
@github-project-automation github-project-automation bot moved this from In review to Done in TRX Dev tracker Nov 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lahm86 lahm86

Labels
Feature New functionality TR1 TR2
Projects
TRX Dev tracker
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

libtrx/config: support enforced config settings lahm86/TRX
4 participants
@rr- @Raildex @lahm86 @aredfan