Interface function replication

Sadly not @Excess3 , or at least in a satisfying way…just found this thread and checked on bug report. It’s marked as “Won’t Fix”, but I don’t see any documented reasoning for that…
Going to questions & answers thread just leads back to this thead.

I mean I didn’t actually expect that replicating interface calls would be intended, but why is this still not supported, if it is officially recognized as a bug, and it has been clearly state that this is intended?

Here’s link to Isse for reference:

This would clarify a lot of animosity surrounding interfaces, at least providing documentation on replication properties of them would be helpful to say least!
let’s keep faith that epic will eventually fix this bug, will not have fizzled out in vain!

By almost 2024, this problem has not been solved yet, and I have also encountered this problem, which is frustrating. Casts will have serious coupling

what is the problem exactly? just use the interface event to call a server RPC

Blueprint interface events cannot be replicated like events, and locally executed blueprint interface events cannot be replicated to the server through event replication

1 Like

no but you can call a server event off the interface event? so same thing with one extra step

Hello,

I try this as suggested (if I understood right) but does not work.
The event fire is called, it goes to call FireSRV but the Event FireSRV never runs, the flow dies where the breakpoint is.
Maybe I am not doing correctly.

ah sorry you probably dont ‘own’ the actor your calling the interface on which means you need to reverse the order.

Have a server RPC call the interface function in your player/controller

Thank you.
I was going to try that, I made work with the interface, my bad.
Will try.

Hello, I’ve tried the setup you’re proposing but I can’t get it to work either. Maybe I misunderstood what you said, is this what you imagined ?

Player BP
image

Object that I don’t control to interact with

Video of what’s happening

where is held actor/interact actor set?

im guessing not on the server and they arent replicated so it likely fails there.

You can see on the second screenshot, it’s supposed to be set after the interface function call but it never reaches here because the code just die before when it’s supposed to run the interface function on the server.

It’s not doing it and fails, it simply doesn’t do it.

i’m talking about your first screenshot, you have two getters with fail branches that you haven’t checked. On Server_Interact

the reason they might fail is the test is on server and they arent replicated so unless they are set on server they’ll be incorrect

Wow ok sorry, I just understood my mistake. Thank you helping me !

Yay 2025… here i was hoping i was using the RPCs wrong or doing something truly crazy as far as replication goes… but no you have to use some jank work around or wait multiple decades

Can we please unreal fix some of the bugs we’ve had for year and years before progressing to newer and newer versions

Glad we have unreal in the state we do currently don’t get me wrong but the amount of posts i stumble on where somethings been broke/jank for 5+ years is a little worrisome

what problem are you having? always works fine for me :open_mouth:

Problem or possible stupidity