[Known] Chatlog no longer differentiates private conversations with NPCS

Reproduction Rate: 100%
Blocker? Not technically
Details:
In the old system, when you talked to an NPC, or an NPC talked to you, it would be tagged as such to differentiate it as NPC/conversational chat.

Examples:
[7/30/2015 10:33:41 AM] Umuri Maxwell: (to Edvard the Wanderer) bye
[7/30/2015 10:33:41 AM] I wrote of this in my journal.
[7/30/2015 10:33:41 AM] Edvard the Wanderer: (to you) Hrm. You clearly are going to need a sword, you don't strike me as a mage and you will definitely not want to be using fists against skeletons. Doesn't work really well, I'm told. There's a sword over there in that weapons rack right behind me, why don't you go get it and come back? I'll be right here. (To end this conversation, type "goodbye" or press the ESC key twice.)
[7/30/2015 10:33:43 AM] Umuri Maxwell: (to Edvard the Wanderer) exit

Currently it does not do this, and includes ugly blank lines:
[11/6/2017 9:48:29 AM] Umuri Maxwell: how are you doing?
[11/6/2017 9:48:29 AM] Owl's Head Town Crier: I am well, thank you!
[11/6/2017 9:48:29 AM]
[11/6/2017 9:48:59 AM] Villager: Hello.
[11/6/2017 9:49:59 AM] Umuri Maxwell: Goodbye.
[11/6/2017 9:49:59 AM] Owl's Head Town Crier: Good tidings, friend!


Can we get the old way back, or at least some tags differentiating NPC speech coming to a character and their conversations out.
This was necccessary for filtering and a few other analytics on the chatlog.

Steps to Reproduce:
1. Talk to an npc
2. Have an adventure
3. Go back through your chatlog weeks later and realize you don't know what is talking to an npc and what is your comments to people nearby.

User Specs:
OS: Windows 7 Service Pack 1 (6.1.7601) 64bit
CPU: AMD Phenom(tm) II X4 980 Processor (4) System RAM: 16346
GPU: AMD Radeon (TM) R9 390 Series GPU RAM: 8169
SotA.EarlyAccess.LIVE.Win.64.685.Date.10.30.17
Area: OwlsHead
Area Display Name: Owl's Head
Loc: (107.1, 73.3, 102.7)
Debug: T3dsc0hlYWR8fCgxMDcuMTA5LCA3My4yNzksIDEwMi42NzcpfCgwLCAtMC45NjYsIDAsIDAuMjU4KXwtMTI0OC45Mzd8MTYuMjE3MTh8NS44NzIwNg==

 

Bug #: 52716, thank you
@Umuri