Plugin debug
#1

Hello!

So, I am developing my first plugin, and just wanted you guys to give opinion and discuss on this one - is it better if plugin has a debug info inside the "samp-server.exe" (which won't be seen on payed hosts since you don't see a running app like you do if the server is home hosted) or simply create a file named "myplugin_debug.txt" (at some location) and write debug info in there (like MySQL plugin from BlueG does)?

Thanks in advance!

Regards,
Fiki!
Reply
#2

In my opinion, the text file logging would probably be the best option.
Reply
#3

Quote:
Originally Posted by 2KY
Посмотреть сообщение
In my opinion, the text file logging would probably be the best option.
Probably yea!

--

One mind just came to me - why wouldn't I make both, I mean I could make a line like #define DEBUG_NORMAL and line #define DEBUG_SAVE and if you keep both lines defined, it will print the debug to "samp-server.exe" (will be seen temporarily -> until you close your server) + save debug in "myplugin_debug.txt" where you'll be able to see debug as long as you don't manually delete it from file!
Reply
#4

Quote:
Originally Posted by ******
Посмотреть сообщение
Why not just use the logprintf function provided?
Well, I probably will use dat w/o that log saving thingy!
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)