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

DreamObjectWorld doesn't cope with conflicting world.fps and world.tick_lag #2020

Open
ike709 opened this issue Oct 6, 2024 · 0 comments
Open

DreamObjectWorld doesn't cope with conflicting world.fps and world.tick_lag #2020

ike709 opened this issue Oct 6, 2024 · 0 comments
Labels
Compiler Involves the OpenDream compiler good first issue Good for newcomers Parity A difference between OpenDream and BYOND implementations Runtime Involves the OpenDream server/runtime

Comments

@ike709
Copy link
Collaborator

ike709 commented Oct 6, 2024

As of #2019 we now handle tick_lag being set on the world object definition. However, we do not cope with tick_lag and fps having conflicting values. We just set one and then the other.

Ideally, we need to resolve conflicts between these vars at compile-time and then just read one of them at runtime.
@ike709 ike709 added good first issue Good for newcomers Compiler Involves the OpenDream compiler Runtime Involves the OpenDream server/runtime Parity A difference between OpenDream and BYOND implementations labels Oct 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
Compiler Involves the OpenDream compiler good first issue Good for newcomers Parity A difference between OpenDream and BYOND implementations Runtime Involves the OpenDream server/runtime
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ike709