Ulysses Stuff > Releases

URM - User Restrictions Module for ULX

<< < (7/12) > >>

The Asian Aimbot:
I would say so, yeah. It's pretty finicky to use, but it's solid and it works.

eriikok:
Hello, I am sorry I have not been paying attention to this thread. I am active on GitHub and look into questions/problems raised there, I am currently investigating the net error. For future reference I would suggest that you bring this up on GitHub, as that is what I frequent the most. I will however try to pay more attention to this thread.

eriikok:
I have reworked the net system so that URM no longer uses ULX's system. It now uses its own net functions, so any conflicts should be resolved.

JamminR:
Eriikok, thank you. Trust us(Team Ulysses), we understand the challenge of monitoring multiple release locations.
You may wish to turn on notifications for this thread, as many ULX users don't use github to monitor discussions and changes, but instead just download and forget.

Do you believe ULib's net functionality was at fault?
Or was it just that, an accidental conflict, perhaps due to concurrent requests?
If you believe ULib fault, please bring up some constructive discussion and reasons explaining why in our Developers corner or Help and Support section.
Thanks. - JamminR

eriikok:
I am not sure why it happened. I could not replicate the error on my local server so I didn't have a chance to pinpoint it. All I know for certain is that if this error continues then somebody has messed with the net library.

I don't know ULib's net system enough to offer anything but speculation. Both URM and ULib bans can contain alot of data, so maybe there is something that happens when they try to send it when the player spawns. It would be interesting to know if players with access to Bans but not URM (or vice versa) would have got this error; that would give more of a inclination of where the problem lies.

Navigation

[0] Message Index

[#] Next page

[*] Previous page