r/RocketLeagueMods • u/rapidz_on_YT • 15d ago
In need of developers
In need of developers
hello there, i'm rapidz, a vibe coder/coder. i have made this project named RocketIDZ, this launcher lets you play rocket league 2020 client with servers, now i have achieved LAN in virtual networks, fixed crashing when loading inventory. and i have hit a wall, i cannot get online access, unless i figure out the required signature/authentication from PsyNet/Psyonix. rocket league requires this in order to allow me configuring my own server. unfortunately, this i cannot do, as i have 0 experience in PsyNet (except for photon and playfab). currently, i need a developer that is able to help me understand/reimplement the required PsyNet communication or patch my rocket league depot (2020) so im able to create real matchmaking, bans, mmr, item shop, trading, etc - instead of having to use LAN as matchmaking (not user-friendly).
if you have experience with PsyNet, rocket league networking, reverse engineering, or backend/server development, please dm me. (discord: rapidz.yt)
1
u/xHebbins 14d ago edited 14d ago
Yeah the Hebnix source will be updated this weekend to have what you need to get online. Download it and ask Claude/Codex to help you understand Rust.
1
u/0xBL4CKP30PL3 13d ago
1
u/xHebbins 13d ago
Have a major bug which I've just patched in 2.2 and testing before release. I didnt want the issue propagating to more people who download the source prior to the bug fixes release. Should be out Friday night Australian time and with that, the source for version 2.2.
1
u/0xBL4CKP30PL3 13d ago
I mean a bug isn't a reason to completely hide the source. All projects have bugs. That's what branches/issues/etc. are for on github.
Might want to remove the "open source" claim from the website since it's not open source right now.
1
u/xHebbins 13d ago
It's less about having to "hide the source" and more about ensuring it doesn't spread to anyone who downloads and builds it now and I possibly lose control to push the patch tomorrow or Friday. The bug results in a possible lack of connectivity with Psyonix servers if the tool is force closed, which was brought to my attention yesterday. My instant response was to private the source code to avoid the issue spreading through anyone trying to edit/build it themselves and issue a warning in the Discord server, where almost everyone who has downloaded has become a member.
The issue has been resolved but I also need to update another part of the tool and ensure it doesn't return before releasing it as a fix. We also haven't officially advertised the tool, and as per my comment here, I was pretty specific in stating that it will be available on the weekend (which I'm aiming for tomorrow and giving myself until Friday).
With respect, for a tool with less than 40 active users (all word of mouth, my comment above is the first time the link has been posted afaik), I'm not going to update every page that mentions open-source and then revert it 24 hours when my time is better suited to getting the update out as fast as possible.
1
u/0xBL4CKP30PL3 13d ago
That's understandable I guess, it's just that there are more conventional ways to handle bugs without hiding the entire repo. Like adding a warning in the README, making a new branch for the fix, opening a bug issue, etc. Anyone intending on building will almost certainly look at the README first.
Not trying to tell you what to do (it's your project), it just looks a little sus when something claims to be open-source with no links to the source.
1
u/xHebbins 13d ago
I hear you, but like I said we are really yet to actually advertise this project and anyone who I have mentioned it to, I've specifically stated the source code is coming this upcoming weekend when I actually have the time to release it. Anyone who is waiting for that to run the application or look through it is no worse off than if I hadn't mentioned it, it's just they are unaware its coming.
5
u/BeetsAndJeaners 15d ago
bro aske Claude bro