You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been working on multiplayer support on MP Compat as I simply can't handle using the vanilla research tree on modded playthroughs, and it was suggested when I did a PR that I try a PR for this project directly as it's still supported, and when going to add SyncMethod into some of the Queue methods I was surprised to see a commented out SyncMethod attribute already present, and as it turns out my solution was very similar to an older commit that seems to have been long commented out since.
Was wondering why this was reverted, if there was any issues discovered with SyncMethods for the queue and a SyncWorker to handle ResearchNodes that haven't become apparent in hours of my testing. In my experience its made the research tree perfectly usable in MP.
Thanks!
The text was updated successfully, but these errors were encountered:
I've been working on multiplayer support on MP Compat as I simply can't handle using the vanilla research tree on modded playthroughs, and it was suggested when I did a PR that I try a PR for this project directly as it's still supported, and when going to add SyncMethod into some of the Queue methods I was surprised to see a commented out SyncMethod attribute already present, and as it turns out my solution was very similar to an older commit that seems to have been long commented out since.
Was wondering why this was reverted, if there was any issues discovered with SyncMethods for the queue and a SyncWorker to handle ResearchNodes that haven't become apparent in hours of my testing. In my experience its made the research tree perfectly usable in MP.
Thanks!
The text was updated successfully, but these errors were encountered: