vDevice – An module for getting user devices

[SomeFedoraGuy (Him)]

best logo:

vD

[yoshicoolTV (coolyoshi)]

I feel defeated, good game well played

[TimeFrenzied (of Xyaery)]

Ggwp

Yours was excellent too, whatd you make it in?

[yoshicoolTV (coolyoshi)]

I made the logo on Krita, a drawing programm

[TimeFrenzied (of Xyaery)]

Just to upstage this using science

Vanadium is found in about 65 different minerals including vanadinite, carnotite and patronite. It is also found in phosphate rock, certain iron ores and some crude oils in the form of organic complexes. Vanadium metal is obtained by reducing vanadium(V) oxide with calcium in a pressure vessel.

[TimeFrenzied (of Xyaery)]

How’d you make the diagonal lines?

[yoshicoolTV (coolyoshi)]

A bit of precision with the Straight Line Tool

[TimeFrenzied (of Xyaery)]

I used photoshop and literally just learned how to make patterns lol

I honestly shouldve made my lines thicker and changed the bg color but i was in class and wanted to go quick

[2jammers]

To anyone in this thread I wouldn’t use this. Using the currently existing functions input and properties is recommended to give an experience that is the same all across devices. Not to mention these methods have been made before and are super unreliable.

[RobIoxArenaEvents]

Why have you tried to compete with my module? Why have you stole my code and put it into your own module without even really giving credit?

Let me just go over what you’ve taken from my stuff and re-implemented into your code:

1. My console device code

My original implementation uses Enum.KeyCode.ButtonA for checking the console device. Your code does the exact same thing except that you return Enums instead of strings.

2. My mobile device code

You have basically ripped my original implementation and tried to replace it with your own implementation. The values are the exact same, no difference whatsoever apart from you returning Enums instead of strings.

Let’s also not forget that your thread title (vDevice – An module for getting user devices) at the time of writing is a near exact copy of my thread title (qDevice - A utility for getting user devices). The shameless ripping off of almost everything I’ve created for qDevice is terrible.

Why should you not use vDevice?

I’m going to go into exact detail why vDevice is just simply not good:

1. This module has ripped off my code exactly and trying to market itself as a better alternative to qDevice, despite it not being a good alternative at all.

2. The code claims itself to be “lightweight”, having less functions than qDevice. This is technically true, but I fail to see how this makes your product better than mine. I built qDevice not to be lightweight, but to pack in as much features as a developer needs, which gives the developer more tooling when using qDevice.

3. qDevice supports way more features than vDevice. And I mean 9-10 functions more, just take a look for yourself!

It is a shame to see that you are copying my code and trying to market it as being better than mine. You could have easily submitted this as a pull request because you’ve literally done one before in my repository. Instead though, you’ve decided to go the childish route.

[TimeFrenzied (of Xyaery)]

You contribute valid points but he’s never really said that his product was better, he said it was an alternative and provided reasons to use his over yours. And I don’t really think there are any reasons in competing if both resources are free, both modules have their use cases.

SOME OF the methods you use are also common methods for finding out devices, and he also did credit you as the inspiration.

@RobIoxArenaEvents

qDevice supports way more features than vDevice. And I mean 9-10 functions more, just take a look for yourself !

One of the selling points of vDevice is that it has less features from my understanding.

@VSCPlays

@NoxhazeI

Won’t having more functions mean more usability and in turn meaning its better than any say “clone”.

I kind of disagree. Take a look at TopbarPlus for example, It has a ton of functions that almost no one uses, so UIShelf was created to solve that issue

@VSCPlays

Lightweight - Has only 3 functions and 3 properties while for qDevice, it has 12 functions [13 in experimental]

Not saying VSC didn’t do anything but not saying he did, seeing as I haven’t used any of these modules and probably wont be for a while.

[VSCPlays]

@RobIoxArenaEvents

Why have you tried to compete with my module?

When you create something, It is expected to have at least one competitor, like take a look at Blade Ball and Deflect for example, Deflect is a game like TF2 Dodgeball in Roblox and it came out in 2022, but around September 2023, an competitor named Blade Ball was born, It uses swords instead of hands

@RobIoxArenaEvents

Why have you stole my code and put it into your own module without even really giving credit?

I didn’t steal code, I learned from your code, If I compared my function to your’s

vDevice	qDevice

I learned from your module, learning ≠ stealing, That’s like saying you stole an painting from a museum when you learned from that painting

@RobIoxArenaEvents

Let’s also not forget that your thread title (vDevice – An module for getting user devices) at the time of writing is a near exact copy of my thread title (qDevice - A utility for getting user devices).

America has a state called Georgia and there is a country called Georgia so America copied the name of the country as-well

@RobIoxArenaEvents

trying to market itself as a better alternative to qDevice

@RobIoxArenaEvents

trying to market it as being better than mine

I am not saying it’s “better” in any form, I never even said that it’s “better”, It’s just an alternative that people can use if they don’t want a bloat of functions, Everyone has different perspectives

@RobIoxArenaEvents

I built qDevice not to be lightweight, but to pack in as much features as a developer needs, which gives the developer more tooling when using qDevice.

@TimeFrenzied already gave a point

@TimeFrenzied

One of the selling points of vDevice is that it has less features from my understanding.

@RobIoxArenaEvents

qDevice supports way more features than vDevice. And I mean 9-10 functions more, just take a look for yourself !

I already counted the functions if you properly read the OP

@VSCPlays

while for qDevice, it has 12 functions [13 in experimental]

@RobIoxArenaEvents

You could have easily submitted this as a pull request because you’ve literally done one before in my repository.

If I were to make a PR, I could break backward compatibility

@RobIoxArenaEvents

Instead though, you’ve decided to go the childish route.

I feel like reinventing the wheel instead of modifying a module and suddenly break backwards compatibility

---

@2jammers

To anyone in this thread I wouldn’t use this. Using the currently existing functions input and properties is recommended to give an experience that is the same all across devices. Not to mention these methods have been made before and are super unreliable.

Instead of being rude in the replies, please provide constructive criticism instead. your rudeness doesn’t help anyone. if you don’t have anything constructive to say, just scram and leave this post alone

[bitsplicer]

pretty low effort, I think that many people would memorize how to write these functions.

[VSCPlays]

I’ve already seen another module that fits perfectly on your feedback

[xChris_vC (Chris)]

Your usual reply template in this category:

How does this compare to PlatformService?

[xChris_vC (Chris)]

If you don’t defend it yourself, don’t criticize others. That’s hypocritical.

In your own words:

It would’ve been better if you actually make it more useful by adding something that Roblox or Luau doesn’t already provide

Then what is vDevice?

[TimeFrenzied (of Xyaery)]

an alternative to qdevice for newer developers or people who dont want function bloatware

[CCTVStudios (D_I)]

I am 99% sure the people in here are mostly criticizing this resource because it was made by VSCPlays.

Its literally just a simple module to save time, yeah, I get some people saying, “This isn’t a super mega effort thing”, While you can just write this code yourself, the whole point is so you don’t copy and paste it everywhere.

And to that 1 person saying he copied him or something, dude you cant own an idea and he literally uses Enums instead of strings like VSCPlays said

Yeah this resource is not super useful, but it does what it says, if there are better alternatives then go use them instead, he posted this in here because he can.

[2jammers]

I’m helping people who come across the thread. It isn’t necessary to start devforum fights.

[Heimskeet (Alkuli)]

@RobIoxArenaEvents

uses Enum.KeyCode.ButtonA for checking the console device

this is the equivalent of telling someone they copied your formula for getting the area of a circle.

It’s a method of doing something that anyone could write, infact when going through button Enums ButtonA is one of the first to come up.