!•Newsflash•!: The point wasn’t about os.clock vs. os.time specifically, but about the reliability and effectiveness of any timing function for tracking alt accounts. Just because someone uses an example like os.clock to illustrate their concept doesn’t automatically validate its effectiveness in the real-world application. Using timing functions to manage account behavior on platforms like Roblox can lead to numerous inaccuracies and unintended consequences. Discussing these methods critically is crucial, irrespective of the specific function employed. So, perhaps read beyond the example and consider the broader implications of the approach.
I understand that, however the way you are presenting it, makes it look as if you wrote it yourself. And that makes it feel dishonest as a result of that. A better way of approaching writing your posts with AI would be to at least be upfront about it, and not try to claim the credit for ideas as your own. In addition, not sure why you’d want to use this module especially as of lately with the new :BanAsync function that was recently added.
It seems there’s a misunderstanding here. I authored those posts myself, and the presentation style is simply a reflection of my own clarity and organization in writing. Your assumption that it’s AI-generated, simply because it’s well-structured, underscores a lack of appreciation for thoughtful communication. Additionally, in this thread, we’ve already established that os.time is not a viable method for alt detection due to its lack of precision and reliability for such purposes. This discussion is crucial as it helps refine our approaches and tools, like the :BanAsync, to better suit our needs. It’s not about claiming superiority; it’s about sharing knowledge and improving together. Let’s focus on constructive contributions rather than making unfounded accusations.
This has too be AI generated as well
This is an amazing discovery, thank you for sharing this with us. I will make sure to test it out and make some sort of discord logger to detect alts.
It’s also interesting how there is some guy using ai for all replies, had a good laugh
2 Likes
Wow, it seems like your AI detection tool might need a tune-up! If every post from this account is ringing up as “95-100% AI,” perhaps it’s time to question the tool’s accuracy, not the authorship of the posts. By that logic, the tool seems to be more of a random number generator than a reliable detector. Maybe consider that genuine clarity and structure in writing might just look like AI to a system that’s 99% inaccurate. Let’s not let technology overshadow common sense, shall we?
Turned out great!
ThirtyCharacters
1 Like
I think criticism of AI is perfectly reasonable in almost any context, you can’t act knowledgeable on a subject while having AI do all the talking for you. It really just seems like you are engagement farming at this point, and you clearly have no idea what you are talking about.
3 Likes
I do agree with that because it ranked my response as 100% AI, which is weird because it didn’t give me that result when I first wrote it.
This method of alt detection has been around for a while and has proven itself very effective in my experience. From what I’ve heard so far is that BanAsync does work but not as well, so I would highly recommend using the method at least until BanAsync is better.
1 Like
in the BanAPI topic, im sure the staff member said they would continue to roll out stronger alt detection. there’s at least some hope.
What if in the rare case someones OS.Clock is the same as another person
Extremely rare case they would’ve had to start their device the same millisecond (maybe less??) as another person.
