PriMoCarbon Posted June 20 Posted June 20 Every time I invite a newcomer to play RAGE-MP on my server, there’s a serious issue with the notification that appears in the background asking the player to allow client-side C# scripts to run on their machine. The big problem is that, for most players connecting for the first time, this notification gets stuck in the background, with no way to bring it to the front and press the OK button twice — often requiring the player to restart Windows. Is the RAGE-MP team going to bring a solution for this (like removing that bugged notification)?
BrutalStrike Posted June 23 Posted June 23 Man, I'm having the same problem as you. I set up a server and wrote C# code to run on the client side (because some commands I use don't work in JS on the client), and now every time my test server changes its IP, everyone complains that this notification freezes their computer =/ The solution is to cry — no one is going to do anything to fix it. I think they added this notification just to mess with people who like using C# on the client!
Xabi Posted June 24 Posted June 24 21 hours ago, BrutalStrike said: Man, I'm having the same problem as you. I set up a server and wrote C# code to run on the client side (because some commands I use don't work in JS on the client), and now every time my test server changes its IP, everyone complains that this notification freezes their computer =/ The solution is to cry — no one is going to do anything to fix it. I think they added this notification just to mess with people who like using C# on the client! Clientside C# is using .NET 3.1 and the support finished time ago, that's the main reason to warn users joining. There's a bug for some people that makes that notification stay there, but that's a different thing and obviously wasn't meant to be like that, but currently the priority is releasing enhanced version compatibility.
BrutalStrike Posted June 24 Posted June 24 Note: This bug affects the MAJORITY of people. That notification is actually useless. Many players don’t even read it, others have no idea what “Clientside C# Scripts” even means. Not to mention the people who don’t understand English very well (like me — thanks, ChatGPT). I don’t know who the “genius” was who thought this notification could somehow provide security for the client… I think the person who came up with this idea will only realize the mess they made when they try to run clientside C# scripts on a public server themselves!
Xabi Posted June 25 Posted June 25 Well, saying "majority of people" when there are few servers using clientside C# isn't too accurate. About the message itself is totally needed to warn people joining the server that they're doing it at their own risk, so they can't blame RAGE in case something happens due to some .NET Core 3.1 vulnerability or so.
BrutalStrike Posted June 25 Posted June 25 (edited) Start up a server with client-side C# scripts and have 100 people join. Maybe then you’ll understand that the MAJORITY will have issues accepting that notification! As for the necessity of the message, I’ll say it again — it’s completely useless. It only exists so RAGE doesn’t feel responsible in case some vulnerability is exploited, but expecting the user not to click OK twice after all the work of downloading and installing RAGE because of that kind of notification is just insane! There’s no way around it, my friend. Like I said, unless you run a public server yourself with client-side C# scripts, you’ll NEVER understand! NEVER! I CAN’T TAKE IT ANYMORE — HAVING TO TEACH NEW PLAYERS TO SWITCH TO WINDOWED MODE JUST TO BE ABLE TO PLAY ON MY SERVER THAT USES CLIENT-SIDE C# SCRIPTS! HELP! Edited June 25 by BrutalStrike
Xabi Posted June 25 Posted June 25 Well, I told you the reason for it to be there, like it or not. It won't be changed/fixed in a short future as there are other priorities.
PriMoCarbon Posted June 25 Author Posted June 25 47 minutes ago, Xabi said: Well, I told you the reason for it to be there, like it or not. It won't be changed/fixed in a short future as there are other priorities. Regrettable! BrutalStrike, just like you said, all that's left for us is to cry! =/
rogercostadev Posted June 25 Posted June 25 Same problem here. The problem is that not even the "priority" updates can be released soon. More than a year after 1.2 was announced and nothing.
Recommended Posts