thetxt/oxide
1
3
Fork 1
Code Issues 12 Pull requests Projects Releases 6 Packages 1 Wiki Activity Actions

add central logger #25

New issue
Open
opened 2025-09-05 17:00:06 +02:00 by thetxt · 2 comments
thetxt commented 2025-09-05 17:00:06 +02:00
Owner
Copy link

implement a central logger that can be used to log events, distinguishing between different levels of severity and modules.
Add config for which levels/modules should be written to a log file, send to stdout/stderr and send ingame to operators

implement a central logger that can be used to log events, distinguishing between different levels of severity and modules. Add config for which levels/modules should be written to a log file, send to stdout/stderr and send ingame to operators
Opoodoop commented 2025-09-05 17:41:53 +02:00
Contributor
Copy link

Do you think it should be implemented with separate functions like log() warn() and error() for each log level or as an argument like log(2) for a log level of 2. In addition, where would be an appropriate place to implement it, in the lib or server?

Do you think it should be implemented with separate functions like log() warn() and error() for each log level or as an argument like log(2) for a log level of 2. In addition, where would be an appropriate place to implement it, in the lib or server?
thetxt commented 2025-09-07 18:09:55 +02:00
Author
Owner
Copy link

I haven't thought a lot about it yet, but I think having separate functions should be cleaner. It would probably make more sense in the lib with an instance of it being part of the central Game struct

I haven't thought a lot about it yet, but I think having separate functions should be cleaner. It would probably make more sense in the lib with an instance of it being part of the central Game struct
thetxt added this to the 0.4.0 milestone 2025-10-28 16:33:28 +01:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
0.4.0
0.3.0
0.3.1
0.3.0
0.2.0
0.1.2
0.1.1
0.1.0
Labels
Clear labels   
complexity
high

  
complexity
low

  
complexity
medium

  
importance
high

  
importance
low

  
importance
medium

  
type
bug
something that should work, but doesn't

  
type
chore
something that should be done at some point, but doesn't really change functionality

  
type
feature suggestion
a feature that should probably be implemented

  
type
missing feature
feature that should really be working by now, but doesn't

No labels
complexity
high
complexity
low
complexity
medium
importance
high
importance
low
importance
medium
type
bug
type
chore
type
feature suggestion
type
missing feature
Milestone
Clear milestone
No items
No milestone
0.4.0
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
thetxt/oxide#25
No description provided.