- Joined
- Dec 16, 2013
- Messages
- 130
- Reaction score
- 83
Howdy,
I usually don't ask these sorts of things, but as I think this is likely easy to implement.
Currently the log message for overheating ships does not tell you which ship is overheating. Just that the overheat timer has started. Could you add some form of identifier to the message so that it could easily be determined what ship is overheating?
Currently the log message looks like:
[SERVER] MAIN CORE STARTED DESTRUCTION: in 900 seconds - started 1508593121173
I would request the message end up looking something like:
[SERVER] MAIN CORE STARTED DESTRUCTION: in 900 seconds - started on my_entity at 1508593121173
Where my_entity would be the database uid for that object.
This would allow me(and others) to have a significantly more reliable method of detecting when ships start overheating. It would also make that log entry more useful for those looking at logs for what happened.
I usually don't ask these sorts of things, but as I think this is likely easy to implement.
Currently the log message for overheating ships does not tell you which ship is overheating. Just that the overheat timer has started. Could you add some form of identifier to the message so that it could easily be determined what ship is overheating?
Currently the log message looks like:
[SERVER] MAIN CORE STARTED DESTRUCTION: in 900 seconds - started 1508593121173
I would request the message end up looking something like:
[SERVER] MAIN CORE STARTED DESTRUCTION: in 900 seconds - started on my_entity at 1508593121173
Where my_entity would be the database uid for that object.
This would allow me(and others) to have a significantly more reliable method of detecting when ships start overheating. It would also make that log entry more useful for those looking at logs for what happened.
