OldUnreal (Engine)

I was playing around with Suppress to hide log spam in serverlogs and increase readability while decreasing file size by dropping redundant data ,
and im curious as to if suppressing stuff stops logging or stops operations,
my assumptuion was it just ignores logging the info starting with =X
but apparently is stops processing as well , if i add Suppress=log  ,
everything still loades, but i can no longer join the server.
it just sits there,
NetComeGo: Open MyLevel 11/08/12 19:19:50 76.xxx.xx.xxx:56287
DevNet: NotifyAcceptingChannel Control 0 server Level dug.MyLevel: Accepted
and the client sits there connecting forever, this also seems to happen when you suppress the gametype log calls.

suppress was not designed to hide the main log function, some things (variables f.e.) are just not being set and some functions may not be called then from what I see and that probably causes the stall

In my experience the most spamlog is usually caused by some mods with warnings, such as the famous accessed none. Those things are usually fixed very quickly, but require the mod to be recompiled and are often not fixed because of that.

Thats explains it i suppose. only you really would have know the answer i guess.

I am actually trying to hide the "loading package x" and"server unlink" messages tho , as they are not that helpful to save into the log for review ( i save backlogs forever) and it makes it easier to scroll though them looking for certain entries , connections , chats , scripterrors etc when there isnt the same 40 packages loading every time a map changes.
i thought about having a program delete lines out of the file , but that messes up the modified dates and messes my sorting.

You can have a program that takes out the lines but preserves the modified date.

Though I never really figured out how modified dates work in Java. (I always managed to make the file seem like it came from the stone age...) It might be some convoluted API call when it comes to C\C++. If you're not a hardcore programmer then you might have to ask around if someone's willing to program such a thing, or atleast give you a few pointers on how to preserve the modified date while still writing to said file.

If you want to not see scriptwarnings then you can Suppress=ScriptWarning and it wont cause any problems. Suppressing the main log function breaks alot of different things, so the least you can do is just suppress the ScriptWarning key.

i considered  it 'could' be done similarly with some sort of File.SetAttribute thing... or worst case change the system date back  before the file was written to match the old access modified dates automatically. not sure it's worth the trouble honesty for me or anyone to make such a specific thing tho. If i didnt try to do such a thing yet after 4 years , it will probably never happen anyway.. hgw many times am i gonna look at the old file logs anyway even..

You could always just append the date and time to the log filename.