LFRP not displaying

I’m on mobile. That is where I primarily play on and I have been noticing for the past couple of days whenever somebody has a LFRP up I cannot see it. I only see the blue dot next to their name. When I click on about, it doesn’t show anything besides the Blue Dot. But if I go to them in person and look at their profile it will tell me what they’re LFRP says then.

Anyone else noticed this? Or is it just me??

2 Likes

This happens to me sometimes. I wonder if in those cases, they simply didn’t type an associated LFRP message.

2 Likes

I figured it was an undocumented change to the UI in order to start the movement towards preventing certain content from being seen outside the area it was permitted in. In the thread about possible UI changes, that was one of the things that had been mentioned as a possible modification.

Those both would be very valid points but even if you don’t type a message it still gives you the default “looking for RP” and I have put up my own custom messages on some of the characters just to check it. And sometimes they don’t pop up. And it’s never been anything vivid, always just “this is my location come hang out”

It seems to be a bug causing the lfrpDesc not to always be included with the character info.

Technical notes to self on where to start looking

It is probably caused by the core service not sending the proper change event on the charinfo resource when the LFRP desc changes, since the LFRP desc is kept in a separate store from the character.

I have actively seen this while messing with core.char.{id}.info instances, it’s really inconsistent when lfrpDesc isn’t included

I’ve just woken up a character, set its lfrp, and did not receive any update on its info instance, nor can I see the description when looking at the character in the client, even after reloading

If it’s of any help here’s a trimmed down log of events I saw:

-> {"id":1,"method":"version","params":{"protocol":"1.2.3"}}
<- {"result":{"protocol":"1.2.3"},"id":1}
-> {"id":2,"method":"auth.auth.login"}
<- {"result":{"payload":null},"id":2}
// various calls to getUser, getPlayer, and subscriptions to info resources omitted
// wakeup
<- {"event":"core.chars.awake.change","data":{"values":{"ciogl4u9gbrqeebmgvcg":{"rid":"core.char.ciogl4u9gbrqeebmgvcg"}}}}
-> {"id":28,"method":"subscribe.core.char.ciogl4u9gbrqeebmgvcg.info"}
<- {"result":{"models":{"core.char.ciogl4u9gbrqeebmgvcg.info":{"about":"This account is automated. It will not role play with you."}}},"id":28}
// lfrp set
<- {"event":"core.char.ciogl4u9gbrqeebmgvcg.change","data":{"values":{"rp":"lfrp"}}}
// about set
<- {"event":"core.char.ciogl4u9gbrqeebmgvcg.info.change","data":{"values":{"about":"This account is automated. It will not role play with you. change"}}}

As can be seen the rp property on the character came through just fine, but the lfrpDesc property on the info was not changed at all
However when the about was updated, that came through just fine
This is also on the test realm, if that matters

1 Like