[DiscordArchive] I'm not sure why it's doing that. I've never run into that issue. Are you using preloaded maps and a
[DiscordArchive] I'm not sure why it's doing that. I've never run into that issue. Are you using preloaded maps and a
Archived author: Revision • Posted: 2022-08-17T20:30:12.087000+00:00
Original source
I'm not sure why it's doing that. I've never run into that issue. Are you using preloaded maps and active waypoints?
Archived author: branon • Posted: 2022-08-17T20:30:44.062000+00:00
Original source
not that I know of
Archived author: branon • Posted: 2022-08-17T20:30:50.054000+00:00
Original source
this should be pretty vanilla
Archived author: branon • Posted: 2022-08-17T20:30:57.227000+00:00
Original source
completely vanilla actually
Archived author: branon • Posted: 2022-08-17T20:31:32.297000+00:00
Original source
I wonder if it's some weird interaction between the AC console and cron... it is looping as fast as it can waiting for input (or something)
Archived author: branon • Posted: 2022-08-17T20:31:49.563000+00:00
Original source
I feel like I didn't see it max out a core when I was just running `./worldserver` in a terminal during the testing phase
Archived author: branon • Posted: 2022-08-17T20:32:07.481000+00:00
Original source
I'll poke at it some more and see if I can confirm or deny that it only happens when cron launches the process
Archived author: Revision • Posted: 2022-08-17T20:34:30.033000+00:00
Original source
Try to not use cron, start it in i.e screen manually. I haven't used cron since I never needed automatic start on boot since the container never restarts.
Archived author: Revision • Posted: 2022-08-17T20:34:42.729000+00:00
Original source
At least it'll help you eliminate cron as the issue
Archived author: branon • Posted: 2022-08-17T20:42:09.878000+00:00
Original source
it is 100% something cron is doing