LibretroAdmin

Have you tried any more recent version? Because that is a very long time ago. Backtracking that would be nearly impossible going back that far.

> Do you know what stable build number was before the de-macrofying slock stuff was? I highly doubt it is that. And it is after 1.10.3 stable anyway (the most...

any feedback yet? @Cthulhu-throwaway you might want to keep an eye on this thread too since its networking related

@alphanu1 Got any ideas here?

Can you guys keep us informed on what the status of this is?

Let's please find a way to compromise here so that neither side here gets alienated and neither side leaves development. We cannot afford any developers to leave over this. We...

@Cthulhu-throwaway We cannot force a particular way of doing things suddenly on the FB Neo team. We have to find a compromise.

I'll repeat again - throwing down ultimatums that one leaves development over a design decision is not productive on either side, and it is unfair and impossible for any of...

> We already have a solution to this issue, which is: stable releases with core snapshots for those releases: http://buildbot.libretro.com/stable/1.10.3/windows/x86_64/RetroArch_cores.7z I agree with this, this is more than enough. We...

> These players are randoms that I just find in the public lobby, simply telling them to update the core isn't possible. Honestly a far better solution is just having...