Skip to content
TORNLIFE More

Attack Logs

Started by PurpleFire [2868362] Committee on in Bugs & Issues.

13 replies · 193 views · thread synced · 3 days ago · View on torn.com
About this thread

Posts archived: 14 / 14 posts (100%) · the total is Torn's reply count + the opening post at the last fetch

Counted by TornLife from the archived posts.

Archived posts
14
Discussion span
→
People posting
5
Likes on archived posts
10
Posts by staff, officers and moderators
13
Authority score
61 / 100
Historical score
44 / 100
Story score
47 / 100
Engagement score
61 / 100

Most-liked replies

PurpleFire [2868362] Committee Committee

 

When reading through attack logs, it is very difficult to read the damage, since it is not separated from the time.


****** fired 9 rounds of his Qsz-92 critically hitting ***** in the Head for 403013:15:34

Screen readers read out the numbers in one continuous 'breath', so it becomes a non-sense number. 


Would it be possible to have something separating the two numbers? Something like:


****** fired 9 rounds of his Qsz-92 critically hitting ***** in the Head for 4030 - 13:15:34

or

****** fired 9 rounds of his Qsz-92 critically hitting ***** in the Head for 4030 life 13:15:34

 

 

Chedburn [1] Admin Developer

I'll ask Constantin to see if he has any ideas to resolve this for those using screen readers or copying and pasting the content.

toshykazu [1435333] Admin Staff

What about now? I've added a label for the time container, it should pronounce the word "time" now. Does it help? 

Thank you.

PurpleFire [2868362] Committee Committee

Thanks!

When reading the log with NVDA, it reads out like this now:
XXX   hit   Leslie   with his Bone Saw in the Stomach for   3020  23:00:39
The timestamp is recognized, and the words hour/minutes/seconds are read out, making it a bit more obvious where the damage ends and the time begins.


The spacing between the damage and timestamp help as it gives a very small pause in the speech, but it does still sound a bit garbled.

When copy pasting the timestamp is lost for screen readers, however. it sounds no different in that respect.

Again, the spacing helps break it down if I scan through it character by character, so I am guessing it does 'look' better at least.


This is an improvement for sure. Still, if there was any way to give a '-' or something along those lines between the damage and timestamp, it would help a lot.

Maybe even a '.' at the end of the damage, to signify the end of a sentence.

 

 

PurpleFire [2868362] Committee Committee

Better than?

The space helped it read slightly better as I mentioned in my previous post.

There is still a bit of runon though.

If a dot were added at the end of the damage, it would force the screen reader to pause as to pause for the end of a sentence.

XXX hit PurpleFire with his Katana in the Stomach for 1221 02:48:49

This does not really cause the screen reader to pause, it is read out in one single breath.


XXX hit PurpleFire with his Katana in the Stomach for 1221. 02:48:49

This forces the reader to pause and makes it very easy to understand.


XXX hit PurpleFire with his Katana in the Stomach for 1221 - 02:48:49

This also forces the reader to pause, making the numbers clear and easy to understand.

 

toshykazu [1435333] Admin Staff

Got it. Initially, I thought that the task was to separate the amount of damage from the time and a space is enough. 

Now I realize that we need to separate the whole sentence so I added a dot at the end. 

 

PurpleFire [2868362] Committee Committee

The space is needed, so everything does not blend in together.

PurpleFire hit XXX with her Samurai Sword in the Right arm for 786.02:48:50

This way it is not recognizing the dot as an end of sentence period.

Instead it is reading out "786dot02:48:50', so it is saying 'dot' rather than pausing.

If a space is added after the '.', it will break up the damage and timestamp in a way that sounds natural and clear.

Like this:

PurpleFire hit XXX with her Samurai Sword in the Right arm for 786. 02:48:50

 

 

 

PurpleFire [2868362] Committee Committee

Hm, I'm noticing no change.

Currently it is showing me this:
XXX fired 2 rounds of his ArmaLite M-15A4 hitting Leslie in the Chest for 3868.17:29:22


So it reads out like this:
XXX fired 2 rounds of his ArmaLite M-15A4 hitting Leslie in the Chest for 3868dot17:29:22


Without the space after the '.', it is just read out all in one breath and instead of recognizing the '.' as a period, it is reading out the word 'dot'.
I imagine it looks a bit off too.


The ideal result would be this:
XXX fired 2 rounds of his ArmaLite M-15A4 hitting Leslie in the Chest for 3868. 17:29:22

Also, thank you for your time, it is much appreciated. :)