is it actually gone tho?

ig but orc is still not dead or is it..

Most of the ORC's appeal isn't even to old roadblocks users anymore - most of those people have probably well moved on - but just as an alternative way to use the client, basically. I am of the opinion that people only care about Old Roadblocks because they associate it with their childhood (I was young in 2016, thus "2016" is like an older Roadblocks for me (even though it isn't "old Roadblocks")) Because, truthfully, who looks at 2008 Roadblocks footage and goes "hell yeah!!" in this day and age unless they associate it with some kind of nostalgia based on their own experience?

That is indeed true and something that I am aware of myself, but:

The 2012 client is still a hellscape of Assembly code that I do not bother to understand (I plausibly could, but I have better and more important things to do than involving in grey area) Again, with the concerns that I have after the said incident, I really do want to be sure that not just the backend, but everything in this revival has at the very least little to no flaws at all, else the potential would be lost to the brim. It already feels like that I am starting to get paranoid, but I just value this revival with the way how it acts 10x more adequate than any other and I do not really want someone oppositional of that (like what could have happened) to kill it just like that.

idk how to put this in green but this blud has no clue what he's talking about #1. it doesnt matter how shitty the client is since debugging it is the same for every client :thumbs_up: #2. im just as clueless as you and it took me 15 minutes to figure out how to debug the 2008 client, and I would imagine the 2016 client isnt have as buggy #3. i hate how you act like you're the mc :pray: :skull:

That is indeed true and something that I am aware of myself, but: The 2012 client is still a hellscape of Assembly code that I do not bother to understand (I plausibly could, but I have better and more important things to do than involving in grey area) Again, with the concerns that I have after the said incident, I really do want to be sure that not just the backend, but everything in this revival has at the very least little to no flaws at all, else the potential would be lost to the brim. It already feels like that I am starting to get paranoid, but I just value this revival with the way how it acts 10x more adequate than any other and I do not really want someone oppositional of that (like what could have happened) to kill it just like that. idk how to put this in green but this blud has no clue what he's talking about #1. it doesnt matter how shitty the client is since debugging it is the same for every client :thumbs_up: #2. im just as clueless as you and it took me 15 minutes to figure out how to debug the 2008 client, and I would imagine the 2016 client isnt have as buggy #3. i hate how you act like you're the mc :pray: :skull:

First off, I am aware about "Debugging" Guides existing on r/oldrobloxrevivals which are factually called Client Patching Guides. About the process being the same for every year? Well, almost. If I remember correctly, patching 2008 and 2013 clients is kind of night and day, especially that they use different rendering engines. "Patching" 2016? It is a different, but more comprehensive experience. That goes without saying.

But since we are talking about patching for revival projects, what about all these vulnerabilities that these guides do not mention how to fix them? Sure, there was the LRRE wiki which explained them, but the last time I checked, their web server was dead and I was not able to find any archives of it. It's not that easy to patch the client to be flawless than how you think it is.

Second, all I just do is be constructive and respectful. What's so bad about it? What's so morally correct about your behavior and slang-style speech which I usually see from people who normalize being rude? If you cannot say anything about it, please do not act like you are better than me. All what I am asking for you is to analyze better and most importantly, be kind. It's better not just for you, but for everyone here. You are probably not going to listen to me simply because I said it, but trust me, you are walking on thin ice with this kind of attitude due to Rule 6.

That is indeed true and something that I am aware of myself, but: The 2012 client is still a hellscape of Assembly code that I do not bother to understand (I plausibly could, but I have better and more important things to do than involving in grey area) Again, with the concerns that I have after the said incident, I really do want to be sure that not just the backend, but everything in this revival has at the very least little to no flaws at all, else the potential would be lost to the brim. It already feels like that I am starting to get paranoid, but I just value this revival with the way how it acts 10x more adequate than any other and I do not really want someone oppositional of that (like what could have happened) to kill it just like that. idk how to put this in green but this blud has no clue what he's talking about #1. it doesnt matter how shitty the client is since debugging it is the same for every client :thumbs_up: #2. im just as clueless as you and it took me 15 minutes to figure out how to debug the 2008 client, and I would imagine the 2016 client isnt have as buggy #3. i hate how you act like you're the mc :pray: :skull:

I AM THE MC!!! RAHHHh!!!!!!!!!!!!!!!!!!!1

i got my amazing self-proclaimed knowledge from davy bazooka, ceo of dynablocks

Anyway I'm literally not talking about debugging, I'm talking about just playing the client itself. 2008 looks like cheeks compared to even just 2018 (minus rthro lol) lets be honest

I AM THE MC!!! RAHHHh!!!!!!!!!!!!!!!!!!!1 i got my amazing self-proclaimed knowledge from davy bazooka, ceo of dynablocks Anyway I'm literally not talking about debugging, I'm talking about just playing the client itself. 2008 looks like cheeks compared to even just 2018 (minus rthro lol) lets be honest

If you did not notice who they were replying to, they were replying to my point about patching clients and et cetera back in Page 1, to be exact.

If you did not notice who they were replying to, *they were replying to my point about patching clients and et cetera back in Page 1, to be exact.*

nevermind, I am ultimately stupid lol

the ORC has always been a volatile place, there is no knowing what could happen to any site at any time whether that be takedown notices, people wanting to exploit or simply cause chaos

it was like this a few years ago and I do not see it changing too much with a lot of recent events nevertheless, it's nice to see a place stick around for four years without any major issues

That is indeed true and something that I am aware of myself, but: The 2012 client is still a hellscape of Assembly code that I do not bother to understand (I plausibly could, but I have better and more important things to do than involving in grey area) Again, with the concerns that I have after the said incident, I really do want to be sure that not just the backend, but everything in this revival has at the very least little to no flaws at all, else the potential would be lost to the brim. It already feels like that I am starting to get paranoid, but I just value this revival with the way how it acts 10x more adequate than any other and I do not really want someone oppositional of that (like what could have happened) to kill it just like that. idk how to put this in green but this blud has no clue what he's talking about #1. it doesnt matter how shitty the client is since debugging it is the same for every client :thumbs_up: #2. im just as clueless as you and it took me 15 minutes to figure out how to debug the 2008 client, and I would imagine the 2016 client isnt have as buggy #3. i hate how you act like you're the mc :pray: :skull:

First off, I am aware about "Debugging" Guides existing on r/oldrobloxrevivals which are factually called Client Patching Guides. About the process being the same for every year? Well, almost. If I remember correctly, patching 2008 and 2013 clients is kind of night and day, especially that they use different rendering engines. "Patching" 2016? It is a different, but more comprehensive experience. That goes without saying.

But since we are talking about patching for revival projects, what about all these vulnerabilities that these guides do not mention how to fix them? Sure, there was the LRRE wiki which explained them, but the last time I checked, their web server was dead and I was not able to find any archives of it. It's not that easy to patch the client to be flawless than how you think it is.

Second, all I just do is be constructive and respectful. What's so bad about it? What's so morally correct about your behavior and slang-style speech which I usually see from people who normalize being rude? If you cannot say anything about it, please do not act like you are better than me. All what I am asking for you is to analyze better and most importantly, be kind. It's better not just for you, but for everyone here. You are probably not going to listen to me simply because I said it, but trust me, you are walking on thin ice with this kind of attitude due to Rule 6.

Sorry I'm late, this sounded very corny, especially you going on about the "rule 6" thing and i don't think you really know what patching is, since the whole point of patching is fixing vulnerabilities, and you said that guides don't go over that? doesn't make much sense

That is indeed true and something that I am aware of myself, but: The 2012 client is still a hellscape of Assembly code that I do not bother to understand (I plausibly could, but I have better and more important things to do than involving in grey area) Again, with the concerns that I have after the said incident, I really do want to be sure that not just the backend, but everything in this revival has at the very least little to no flaws at all, else the potential would be lost to the brim. It already feels like that I am starting to get paranoid, but I just value this revival with the way how it acts 10x more adequate than any other and I do not really want someone oppositional of that (like what could have happened) to kill it just like that. idk how to put this in green but this blud has no clue what he's talking about #1. it doesnt matter how shitty the client is since debugging it is the same for every client :thumbs_up: #2. im just as clueless as you and it took me 15 minutes to figure out how to debug the 2008 client, and I would imagine the 2016 client isnt have as buggy #3. i hate how you act like you're the mc :pray: :skull: First off, I am aware about "Debugging" Guides existing on r/oldrobloxrevivals which are factually called Client Patching Guides. About the process being the same for every year? Well, almost. If I remember correctly, patching 2008 and 2013 clients is kind of night and day, especially that they use different rendering engines. "Patching" 2016? It is a different, but more comprehensive experience. That goes without saying. But since we are talking about patching for revival projects, what about all these vulnerabilities that these guides do not mention how to fix them? Sure, there was the LRRE wiki which explained them, but the last time I checked, their web server was dead and I was not able to find any archives of it. It's not that easy to patch the client to be flawless than how you think it is. Second, all I just do is be constructive and respectful. What's so bad about it? What's so morally correct about your behavior and slang-style speech which I usually see from people who normalize being rude? If you cannot say anything about it, please do not act like you are better than me. All what I am asking for you is to analyze better and most importantly, be kind. It's better not just for you, but for everyone here. You are probably not going to listen to me simply because I said it, but trust me, you are walking on thin ice with this kind of attitude due to Rule 6. Sorry I'm late, this sounded very corny, especially you going on about the "rule 6" thing and i don't think you really know what patching is, since the whole point of patching is fixing vulnerabilities, and you said that guides don't go over that? doesn't make much sense

1. About the "Rule 6 thing", it's really silly how you use the word "thing" as if you do not understand what it is. In the Rules page, Rule 6 mentions that "You are not allowed to bully users", when you literally bullied users with the recent Russian posts just because they spoke a foreign language.
2. The guides go over the basic vulnerability patching, which means that they do not explain every patchable vulnerability. If we want finobe.net's clients to be flawless, then the Team must patch every vulnerability in them.