Bindfile loads dumping in Sys window?

[Shenanigunner]

I (obviously) load bindfiles frequently, especially right now as I'm going through and doing a wholesale update of my bind, file and tweaks setup.

 

Every time I load a bindfile, the entire contents read out in the System window. I don't recall that ever happening before. Is this a dev/update change, can it be changed back, and is there an option I am overlooking to suppress it?

 

(No, it's not a bindloadfilesilent thing. Using ...silent just doesn't give any file-loaded response, but the stream of content still goes pasts. Annoying.)

[Ironblade]

On 1/27/2024 at 2:36 PM, Shenanigunner said:

Every time I load a bindfile, the entire contents read out in the System window. I don't recall that ever happening before. Is this a dev/update change,

 

If it was a change, it wasn't recent.  I don't remember it ever working differently.

[AboveTheChemist]

I tested some of my normal bind files last night, both on Live and on Brainstorm, and did not see the bind file contents printed to the Sys channel in either case.

 

The only time I recall seeing bind file contents printed to the Sys channel is when I load in a special settitle bind file. It's a bind file embedded with 2550 settitle commands meant to determine which badges a character has. It has printed to the Sys channel for as long as I can remember, and I've been using it for years. I've included a copy here in case there is something in there that gives a hint as to why your bindfiles are printing to the Sys channel.

 

settitle_all_1.txt

[WanderingAries]

Isn't that how that function works though? In order to grab the badges (for example) it had to literally print it to a certain tab (or maybe it just read that tab?).

[Shenanigunner]

Hmm. I've loading bindfiles for lo these many years, and I don't recall ever seeing a pink-text dump spin by. Maybe it's one of the system channels I have never had activated before... I'll look when I log in. I am rebuilding my bindfile setup for all alts and I may have copied a variant options or chat file across them.

[American Decoy]

I load bind files, and I never see more than the fact that the text file is called.  I don't see the line-by-line text of the file.  I even have mine set to say it in local, so I know when I accidently hit a key that loads more bind text files.

[AboveTheChemist]

17 hours ago, Shenanigunner said:

I've loading bindfiles for lo these many years, and I don't recall ever seeing a pink-text dump spin by.

 

The text I see go by with the settitle bind file I posted above isn't pink, I think it is either yellow or green (can't recall offhand) so I think it might be going to a different channel (assuming neither one of us has changed the default colors of our chat channels). I know the pink text channel you mention because I /conprint a lot of stuff now and that is the channel it goes to (and the wiki says that is the Sys channel). I'll have to check tonight and find out the exact name of the channel the settitle binds go to. I just assumed that it was the Sys channel but I now highly doubt my assumption.

 

Also, can you post a screenshot of what you are seeing? It's probably a long shot but there may be a clue in there.

[Shenanigunner]

55 minutes ago, AboveTheChemist said:

I just assumed that it was the Sys channel but I now highly doubt my assumption.

 

Just to clarify —

• I've (obviously) been loading bindfiles by the gross and almost every playing session for a long, long time.
• I have always seen the green-text "bindfile blah blah blah" has been loaded. Sometimes I ...silent that, and sometimes I combine silent load with an SG channel message "Special bindfile blah blah loaded."
• I don't recall ever seeing a full run-past dump of a bindfile in any window.
• I now see that full display/dump every time, even using silent, in pink, in the System tab, which has only four defined channels (all the system-y garbage and notices) but nothing actually named System, which I assume is inherent.

The only change, over many years, as I said, is that I am doing a wholesale cleanup of my UIs and bindfile system and might have copied chat or options from one alt that had an anomalous setting. (Hmm. Need to load a dead alt to see if that one is also affected.)

 

So I'm baffled. Either I've been the outlier, never seeing this pink dumpage, or something has changed in the last release or two.

[Shenanigunner]

 

Well, that's weird. I loaded an alt so old I had to go find his bindfile, and a silent load produced no visible response, while a non-silent load showed only a message like that green one.

 

Saved chat and options, loaded my main, loaded chat and options, and it worked... once. Then every bindfile load produced either the result shown, with the alternating yellow and pink responses, or just the pink ones. I am utterly baffled.

 

I mean, it's trivial — everything is working perfectly — but it's annoying, it's not been a usual thing and I'd like it to go away.

 

 

Edited January 30 by Shenanigunner

[AboveTheChemist]

If you would be willing to share one of your bindfiles that exhibits the issue, I can create a dummy character tonight and try to load it and see if I can replicate the issue on my end. That way, if it's a quirk in your files causing the issue, perhaps we can find it. In your screenshot above, the yellow text that just says 'bind' looks like the feedback I get from the settitle bind I posted, but I honestly don't think I've ever seen anything like the pink text from loading a bind file.

[Shenanigunner]

I'm happy to share the files, but there's nothing faulty about them (I know sometimes a misplaced quote or other character can cause all kindza fun), and older, well-vetted files are doing it, too.

 

This is new configuration I'm working out, putting the bulk of standardized binds in one file so that updates can be readily shared among all alts — it's been a PITA to remember to load a patch file for every alt, a pointlessly complicated method — while the alt's binds are in a secondary file.

 

These don't include a number of secondary and rolling-bind files. (Caveat: I will probably delete these in a day or so just to keep some work in progress from cluttering the bitstream. A full release of prototype files and the guide is RSN.)

 

COMMON.txt Shenanigunner.txt

[Shenanigunner]

25 minutes ago, Shenanigunner said:

I'm happy to share the files, but there's nothing faulty about them (I know sometimes a misplaced quote or other character can cause all kindza fun), and older, well-vetted files are doing it, too.

 

This is new configuration schema I'm working out, putting the bulk of standardized binds in one file so that updates can be readily shared among all alts — it's been a PITA to remember to load a patch file for every alt, a pointlessly complicated method — while the alt's binds are in a secondary file.

 

These don't include a number of secondary and rolling-bind files. (Caveat: I will probably delete these in a day or so just to keep some work in progress from cluttering the bitstream. A full release of prototype files and the guide is RSN.)

 

The only odd thing I'm doing is using the semicolon for comments, since there are no provisions for "ignore this line" in the bindfile parsing. It writes the comment string to the semicolon bind, each time, and thus it requires either a final null bind ( ; "" ) or, if you want to bind something to semicolon, that bind as the last in the file. But the weird behavior happens with and without this feature in use.

 

 

 

 

 

Shenanigunner.txt COMMON.txt

Edited January 30 by Shenanigunner

[Ironblade]

Well, it's a mystery to me.  I wonder if there's some setting that one of us changed and forgot about.

This is what it looks like when I load binds and it has always looked like this for me.

 

Edit:  By the way, this display is wonky as hell.  Each load, it only displays about 14 of the bind commands from a file that has like four dozen.  They all load correctly, but only a handful are displayed.  And it doesn't display the same ones each time.  Not sure what that means, if anything.

 

Edited January 30 by Ironblade

[Shenanigunner]

I just loaded another completely cold alt and loaded first her old bindfile - no "dump" - then my new common file - dump! - and then the original bindfile again - no dump. So something is going on with my new files, but g'damn if I can figure out what. Arrrrrgh.

[DoctorDitko]

Will diffing the two files narrow things down, or just add noise?

[AboveTheChemist]

It appears to be the blank lines in between groups of binds causing the issue. I ran it as-is and saw the same output as your screenshot (more on that below). I removed the blank lines and it loaded without echoing the pink/yellow text to Sys. I noticed also that the text echoed in pink were the lines preceding each blank line.

 

Oddly, when I loaded in the file as-is, this is what was reported in green text at the end:

 

2024-01-30 21:11:47 Keybinds file loaded: c:/Games/HC/accounts/<my_account_name>/Logs/chatlog 2024-01-30

 

When I loaded it after removing the blank lines, this is what was reported (I renamed the file to shen_temp.txt):

 

2024-01-30 21:12:36 Keybinds file loaded: c:/Games/HC/settings/beta/shen_temp.txt

 

I thought maybe one of the file load/save binds was being triggered and trying to call a file that I don't have, but I removed all lines that tried to load or save a file and it still reported as trying to load my chatlog, so I am stumped as to what was happening there.

Edited January 31 by AboveTheChemist

[Ironblade]

20 hours ago, AboveTheChemist said:

It appears to be the blank lines in between groups of binds causing the issue. I ran it as-is and saw the same output as your screenshot (more on that below). I removed the blank lines and it loaded without echoing the pink/yellow text to Sys. I noticed also that the text echoed in pink were the lines preceding each blank line.

Oh, very good.  Yes, that does seem to be what is going on.  Good to know.  I'm going to leave the blank lines in because it makes the file easier for me to read.

[DoctorDitko]

Can't you leave a comment marker on empty lines for the best of both worlds?

;

or

#

Or am I thinking of another game?

 

(Forgive me if so. I'm getting old. I knew I was older than Star Trek, but I recently realized I'm also older than Doctor Who. >sigh<)

 

 

Edited February 1 by DoctorDitko

[Shenanigunner]

For what it's worth, the problem has gone away with what are now completely clean bindfiles. I can clear binds, load the base file, load the alt file and then load a special overlay file... no streams of pink or yellow dump. But for whatever reason, once in a while, while reloading this or that, I'll get the streams.

 

I'll experiment with blank lines, but I am pretty sure I loaded files with separating lines without all the noise.

 

There are no formal comment markers, but what I've come to use is the semicolon. It limits you to one line, it does clog up one bind slot with each re/load, and you HAVE to end with either a ; "nop" or a valid bind to the semicolon. Best I have found.

 

Thanks for all the testing and feedback. The GABB update (now GABS) is almost done and it's... a huge improvement on the old version.

[Shenanigunner]

Figured it out:

• If your bindfile has no empty lines, you get no error or system messages at all.
• If you have empty lines, you get the repeat of the bind in pink.
• If you don't use the ...silent option, you also get the yellow 'bind' responses for each empty line.

 

So don't use blank lines if you want to avoid the (to me) annoying splashback. I know some use them to break up the files, but you can use the semicolon-comment trick instead, like so:

 

B Bind something to B
C Bind something to C
; -----------
D Bind something to D
E Bind something to E
; nop

 

Just don't forget that last nop or assignment.

 

 

Edited February 2 by Shenanigunner