Grid Sage Forums
- November 24, 2024, 10:35:43 PM
- Welcome, Guest
|
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
1
Ideas / Re: Save all messages to the scores/*.txt file
« on: May 31, 2015, 09:22:56 PM »
Oh, I just saw the thread about logging turn counts. This would work well with my above idea, as syslogs usually contain meta tag and date/time before the info data. Just replace date/time with turn number.
I'm beginning to think I read WAY too many syslogs.
I'm beginning to think I read WAY too many syslogs.
2
Ideas / Re: Save all messages to the scores/*.txt file
« on: May 31, 2015, 09:16:20 PM »
Hi, I just found out about this game today, and was reading up on it. I saw this thread, and while I haven't bought the game yet, I thought I could add an idea about "verbose or not" on log file versus screen logs. If it is WAY off, I apologize in advance. From the looks of what I have seen, this game appears to be a MUST PLAY as soon I get some time to do so. Please to don't be to harsh if I'm totally off base with this idea, it comes from a good, if ignorant, place. 
I read computer logs a lot at my job. Syslogs, event log, and such. Those usually contain level info at the start of the line so they can be sorted easily.
ie : (1) critical , (2) warning , (3) info, (4) debug and such schemes. So, when I view them either in realtime or reviewing old logs, I can have it only display the level I want to see, but still have the other levels still in the log. If I select level 1, I only see level 1. If I select level 2, I see both 1 and 2. If I select whatever the largest level is, I see every detail.
Since you said that the message log is only stored in one place, you could place this info on each line there, and still have it in one place. Then you can have an option where the player could select what is shown on the screen log, and it would just parse out and not display the unwanted lines, and possibly not show the "level" meta tag either. ( You could also use the meta tag to colorize the log) You could even make the option available for what is written the final log file, so the level of verbosity could be controlled there also.
Levels could be things like : (1) general , (2) terminal output, (3) equip action, (4) battle actions, and so on. You could do a simple select level and show all < selected, or a discreet selection of items by checkbox, like just general and equip action, but not hacking terminal.
As added bonus, if you leave the the meta tags in the final txt file, there lots of ways/tools to filter text out there. Players could use that to quickly just view haciking terminal text lines, battle reports, or whatever they want to see post game. Or even use the tags to colorize it, like a I do with those system logs.
TL;DR - use line tags to classify/sort/filter/display log entries
On a different note, even though I see that the text file is only produced on death, the systems geek in me would love for it, or a currentgame.txt, to be appended on event/realtime. Then I could setup something to follow the file and display it realtime on the machine/monitor I already have showing various logs. (think tail -f ) I could even setup something to colorize the lines using meta tags in realtime. But of course I'm used to looking at things like that, and think it would be cool putting this into other tools I use, or displaying on my tablet. Not something for everyone tastes, I know, but I also love it when games allow me to display info outside of main display.
Hope I'm not too out of line here, but since the idea has been around a long time for monitoring logs, I figure it should not be to hard to find examples of how to do all that. Plus for simple logs, I prefer this to using XML or some such. Easier to parse, and easier for people to read, since it is looks like a play script. Thanks for reading!
I read computer logs a lot at my job. Syslogs, event log, and such. Those usually contain level info at the start of the line so they can be sorted easily.
ie : (1) critical , (2) warning , (3) info, (4) debug and such schemes. So, when I view them either in realtime or reviewing old logs, I can have it only display the level I want to see, but still have the other levels still in the log. If I select level 1, I only see level 1. If I select level 2, I see both 1 and 2. If I select whatever the largest level is, I see every detail.
Since you said that the message log is only stored in one place, you could place this info on each line there, and still have it in one place. Then you can have an option where the player could select what is shown on the screen log, and it would just parse out and not display the unwanted lines, and possibly not show the "level" meta tag either. ( You could also use the meta tag to colorize the log) You could even make the option available for what is written the final log file, so the level of verbosity could be controlled there also.
Levels could be things like : (1) general , (2) terminal output, (3) equip action, (4) battle actions, and so on. You could do a simple select level and show all < selected, or a discreet selection of items by checkbox, like just general and equip action, but not hacking terminal.
As added bonus, if you leave the the meta tags in the final txt file, there lots of ways/tools to filter text out there. Players could use that to quickly just view haciking terminal text lines, battle reports, or whatever they want to see post game. Or even use the tags to colorize it, like a I do with those system logs.
TL;DR - use line tags to classify/sort/filter/display log entries
On a different note, even though I see that the text file is only produced on death, the systems geek in me would love for it, or a currentgame.txt, to be appended on event/realtime. Then I could setup something to follow the file and display it realtime on the machine/monitor I already have showing various logs. (think tail -f ) I could even setup something to colorize the lines using meta tags in realtime.
But of course I'm used to looking at things like that, and think it would be cool putting this into other tools I use, or displaying on my tablet. Not something for everyone tastes, I know, but I also love it when games allow me to display info outside of main display. Hope I'm not too out of line here, but since the idea has been around a long time for monitoring logs, I figure it should not be to hard to find examples of how to do all that. Plus for simple logs, I prefer this to using XML or some such. Easier to parse, and easier for people to read, since it is looks like a play script. Thanks for reading!
Pages: [1]