Skip to content

Fix logcleaner to use ticks#5727

Merged
ab9rf merged 5 commits intoDFHack:developfrom
Bumber64:logcleaner-ticks
Mar 2, 2026
Merged

Fix logcleaner to use ticks#5727
ab9rf merged 5 commits intoDFHack:developfrom
Bumber64:logcleaner-ticks

Conversation

@Bumber64
Copy link
Contributor

@Bumber64 Bumber64 commented Mar 2, 2026

Fixed logcleaner to use ticks instead of frames, using autolabor as reference. Also corrected docs that it runs "approximately" every 100 ticks.

@Bumber64
Copy link
Contributor Author

Bumber64 commented Mar 2, 2026

Looks like it works.

I copied the <= cycle condition from autolabor which causes it to run every 98 ticks. Feels like that should be changed? Someone probably forgot to remove the = after inverting it.

* Update logcleaner.cpp
* Update autolabor.cpp
}

if (world->frame_counter - cycle_timestamp <= CYCLE_TICKS)
if (world->frame_counter - cycle_timestamp < CYCLE_TICKS)
Copy link
Member

@ab9rf ab9rf Mar 2, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

while there might be merit to this change, it's unnecessary to dealing with a defect in a pending release. feel free to repropose in a separate PR

even when not in a pre-release feature freeze it's best to keep PRs to a single issue, and a PR that is intended to fix a defect in a imminently pending release should absolutely only address the specific defect and nothing else

@ab9rf ab9rf merged commit 8a89563 into DFHack:develop Mar 2, 2026
14 checks passed
@Bumber64 Bumber64 deleted the logcleaner-ticks branch March 2, 2026 14:14
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

Successfully merging this pull request may close these issues.

2 participants