How can I print all server logs (prints, errors, warnings) into the client F9 screen?

Help and Feedback Scripting Support
,
#1

I want to be able to print every output log from the server (all prints, errors and warns) into the client F9 Developer Console screen. Is there any way to do that? I have looked around before and nobody seems to have done this before.

It would help me out a lot as I have a singleplayer game which I suspect is having issues in a ServerScript, but it’s not replicable on my end consistently and clients playing aren’t logging any issues (because, most likely, the culprate is a ServerScript) so I’m left in the dark to what the problem might be.

If you know how can I do this, please help!!!

1 Like
#2

Is automatically appeals on the F9 Dev Console, you don’t need to change anything.

#3

Server side prints, errors and warns do NOT appear for the client. Only the server. You can see those because you are the owner of the place, but players aren’t able to see server logs. I need something that relays those back to the client.

#4

You can view all your game errors when played from all players in your game analytics>error report, including all clients and servers. The prints and warns, I don’t know how, you should just play your game as an owner

#5

Not sure why you would want to do this, but your best option is probably remote events or LogService

#6

Something like

LogService.MessageOut:Connect(function(message, messageType)
 remoteEvent:FireAllClients(message, messageType)
end)
2 Likes
#7

Again, the error isn’t replicable on my end. Only certain players get it sometimes. I don’t know why and I think the culprate is a server script. I can’t just join them because it’s a singleplayer game.

#8

This is why, read the post:

I’ll try your solution out and see, thanks!

#9

Wouldn’t it just be easier to check live server-side error reports instead of requesting information from players? Just a suggestion.

:link: Error Report | Documentation - Roblox Creator Hub

#10

Hello, the mysterious error isn’t something obvious. I’ve tried looking through error report and “fixing” it multiple times. I am already aware that this is not the best practice, but this error happens to SOME players RARELY, and it is fixed with a rejoin (rejoining does nothing special on the script-side).

I’ve tried replicating it thousands of times by joining on my phone with mobile data, local test, asking friends… etc. It is not possible for me to replicate this consistently, but I keep getting the odd report of players getting softlocked for it. When this happens, I want to have a full view of what exactly the output is both on the client and the server.

#11

Works flawlessly, thanks!
image

1 Like
#12

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.