LoadLibrary is going to be removed on February 3rd

I’ve seen loadlibrary in one script. Probably F3X’s modules. I never really got to use 'em!

3 Likes

Thing is, even though its rare, i still allow some gear items in my games, not deadly or destructive items, like social items or musical, it allows people to enjoy the game along with there own items and experience the game in a personal way. I do know of a few other games that do the same, so ill be a bit sad to see any of these gears get destroyed and never repaired, my games will loose a little something…

9 Likes

This is an extremely niche case and not significant enough to justify focusing on repairing gear, unless there’s someone in the office who just has that much time or drive to do that.

Most of the aforementioned items (social and musical gears) are commonly recreated by the developers and made publicly available through some means of gaining it or sold as either developer products, game passes or purchasables with in-game currency. Sometimes, these custom made gears or edits to existing gears work better than current ones.

A large portion of games that do allow owned gear are commonly legacy games which aren’t supported any longer in the same way gears are legacy (or if they aren’t, I assume they will be eventually).

2 Likes

dues this mean its planned just to abandon gear all together?

4 Likes

I strongly doubt that gear will be discontinued, but it probably won’t be completely supported either. I’m mostly speaking from what I know as well as what’s been seen in and around the platform. There are very few remaining games that still use raw gear from the catalog. Most games custom make their own gear or only use certain pieces of gear (e.g. their meshes).

In the case that you do see catalog gears being used in games, they are often heavily modified versions tailored for the game (such as changing values, making it work with game systems, fixing it, so on). An example could be Epic Minigames. The game does use catalog gear but it looks to be sandboxed to fit game systems. I have no way to prove this as I’m not a developer but the suggestion of that being the case is very strong.

What I am mainly trying to say is that it’s unlikely that gears will be repaired or updated without probable cause for doing so (like with any other case of accepting feature requests and turning them into actual features). As it is, most gear is incompatible with R15, hence lack of updates.

7 Likes

Its not even what you mean by ROBLOX Gear, from the catalog. “LoadLibrary” is a broad term to what the functions were actually like.

function weldObject(x, y)
    local cf = CFrame.new(x.Position)
    local c0 = x.CFrame:toObjectSpace(cf)
    local c1 = y.CFrame:toObjectSpace(cf)
    assert(LoadLibrary("RbxUtility")).Create("Weld"){
        Part0 = x,
        Part1 = y,
        C0 = c0,
        C1 = c1,
        Parent = x,
    }
end

function combineParts(object)
    if script.Parent:FindFirstChild("Handle") then
        if object:IsA("BasePart") then
            weldObject(script.Parent.Handle, object)
            object.Anchored = false
        else
            table.foreach(object:GetChildren(), function(i, c)
                combineParts(c)
            end)
        end
    end
end

combineParts(script.Parent)

This is just an example of a freemodel welding script that puts parts together in a tool when there aren’t any welds, which is usually found in all types of gear. LoadLibrary like used in this, has widely been used within free models for over the past half decade.

From what I’ve seen, LoadLibrary has been used in leaderboards, admins, music players, gun systems, sound bars, dubstep guns, of course gear, and more…

Although.

@mkhamster gave a very practical solution which ensures that scripts won’t break using the LoadLibrary functions.

I think maybe automatically loading the modules into a client limited service like ReplicatedStorage, would be a good address point that the LoadLibrary functions could redirect to.

8 Likes

When i downloaded LoadLibrary.rbxmx it doesn’t let me open it and shows as blank icon, i tried to open it on roblox studio, it didn’t show and doesn’t let me, it only said that there is no type of program like this .rbxmx and what is the issue i despertly needed the modulescripts but i unable to get it, without loadlibrary npcs wouldn’t work as attempt to call string value. :frowning:
If you could share me supported place loadlibrary i would appreciate your help.

3 Likes

you can insert the file into a roblox place by clicking insert from file in the explorer (shown below)

5 Likes

I honestly see this as unacceptable, users have paid robuxs that come from IRL money, and you going to be telling users the gear won’t work anymore. What! At the very least you should take a few hours to fix this.

This is what many users are saying, but I believe this to be false. Lots of wargroups use :gear for that matter, many games have the speed coil gear or make a cheaper gamepass for the same gear in there game only and theres more gear that places use too.

13 Likes

I personally think that if there ends up being no sort of “one size fits all” solution, then someone could spend time going through gear after gear and develop a model of sorts that would fix the broken gears whenever people who own them join the game. That would be labor intensive though.

2 Likes

I think you’re missing the entire point of the response and the thread. This is not a good counterargument towards a response in regards to game security at all. You paid Robux for the gear so just use it as an aesthetic for your character just like you use hats.

Roblox has no reason to continue supporting a scarcely used feature. It’s a waste of engineering resources and time. A majority of games don’t allow user-bought gear in their game as it stands.


It’s not false. Roleplaying groups are still a niche use case to continue to support gear in comparison to the entire platform. “War groups” are not a significant part of Roblox at all.

The gear command is typically only used as a substitute when the developers are too lazy to make dedicated equipment for their places or, for whatever reason, want to use catalog gear independent of their games’ systems.

Games don’t use gear from the catalog raw. The whole point of my response was that developers recreate catalog gear or modify it in some way to have it present in their game.


Your intention was to disagree with me, but you’re simply supporting my point here. Developers create game passes to sell existing catalog gear and modify it to work with their games. They don’t just raw insert catalog gear.

Some (not many) games may still use “catalog gear”, sure, but not in the sense that they directly insert a tool from the catalog or tick off one of the “Allowed Gear” options. They use it as a reference point to refactor the code behind it or modify it, or just to use the mesh it has. See:

Not a significant enough reason to continue supporting gear, much less overhaul 20+ pages worth of gear in order to be compatible with current platform standards (including FilteringEnabled). It’s a waste of time and there’s more interest towards future platform prospects.


Please point out to me one game with a significantly large playerbase that uses catalog gear in the sense that an Allowed Gear option is ticked off rather than the gear being modified to work with game systems (e.g. Epic Minigames modifies tools to get rid of extraneous effects such as healing from drinks gears and changes swords to function with certain minigames).

3 Likes

@zeuxcg It might be an easy shortcut for you guys but you can’t just remove this thing that half the catalog of gear uses! If you aren’t aware, some players still play with unmodified gear and have gear fights including me. The fe update already destroyed enough gear as it is, I can’t begin to count how many of my friends quit because they couldn’t use their favorite gear or play their favorite game after the fe update. You guys can’t keep taking these harmful shortcuts. Just because it doesn’t effect the most popular games doesn’t mean you can just ignore it, that’s unfair to your community. :frowning:

6 Likes

They can remove it, they are going to remove it and they should remove it. It’s been deprecated for years. Preventing platform development for extremely niche cases is unfair to engineers and the rest of us waiting for engine updates.

“Some players still play with unmodified gear” isn’t a significant statistic or reason why this update should be held back or cancelled. Please read the thread for the reasoning on why this choice was made

The platform is going to continue moving forward and if your friends don’t want to adapt, that’s their choice. If FE broke their favourite games, it’s up to the game developer to update their game; you can’t lay it on Roblox for something that is not their responsibility.

This update is literally not a harmful shortcut, it’s a benefit. I would much rather see a long-deprecated functionality removed and unblock some paths in internal development over keeping the feature because a small section of the community arbitrarily allows gear in their games for whatever reason.

This isn’t unfair to the community. Games hardly support raw gear anymore, opting to make their own equipment or modify gears to fit their game systems.

12 Likes

Why do statistics mean more than your player’s wishes? All these updates are taking away children’s favorite games and they don’t have any way to get it back, weather it’s because the developer isn’t active or it’s because gear won’t get updated. There are whole communities based around gear that go under the radar and are effected by these harmful updates and they never get to voice their opinion because their statistic isn’t large enough. Can’t you try and work out another solution or change so that it doesn’t cause more problems by trying to fix a problem? Ever since 2016 gear has been destroyed more and more and people like me have gotten effected by it. Any time we’ve tried to bring up the need for change we’ve just been ignored and this is a perfect example. I don’t want anything bad for roblox, I don’t want to make it harder for roblox, I just want my game back. :confused:

4 Likes

Not everyone’s wishes can come true. Accounting for the majority of developers and future prospects is much more valuable than keeping a deprecated, unsupported feature actively blocking internal development and expending engineering resources just to keep a small niche happy that refuses to familiarise themselves with platform updates (see: your thread on wanting to disable FE because you don’t want to learn it).

Statistics matter because they help show a feature’s use and drive decisions behind it (see: genre sorts removed because of declining use and failure from developers to set game genres, as one could not be set by default). Almost no game with a significant playerbase uses the Allowed Gear setting. There’s no point to supporting gear. It’s relegated as an aesthetic.

Again, the removal of LoadLibrary is not harmful at all, please read the OP for information regarding it’s removal. Your posts are more focused on a specific use case rather than addressing the context of the thread. If there are communities based around gear (which I don’t know of any), then it’s up to them to fork gear and modify them to work in their games.

LoadLibrary will only cause a problem for games that are, for whatever reason, still arbitrarily allowing gear use in their games (I will concede for social gears in places like showcases, but AFAIK those don’t use LoadLibrary). It otherwise has benefits in terms of removing barriers to internal development and dropping support for a feature that’s been deprecated for years. You should not be using deprecated items in your work and use of LoadLibrary has warned of such deprecations.

You keep bringing up this point about the update being harmful or you’re being ignored but you aren’t actually bringing any legitimate points to the table. You can’t be ignored if your initial statement wasn’t a question or request, nor if you haven’t spoken about this widely before; your first post was instead a complaint about gears breaking because of FE and LL’s removal despite those being beneficial.

How is this update harmful? What non-niche cases will it actively break across the platform that cannot be solved by

  • Forking copies of the libraries in the OP or Roblox GitHub repository and replacing LoadLibrary with requires on those modules

  • Learning how to make your game FilteringEnabled instead of finding workarounds

  • Integrating gear with your game systems (see: Epic Minigames, as well as the above point)

  • Not using catalog gear and scripting your own equipment for your games as wanted

?

Sorry for my brevity but someone’s gotta tell you: you’re fighting a losing battle. Engineering will be following through with LoadLibrary’s removal as scheduled in the OP and it is almost certain gear will not be repaired without significant cause for doing so. Engineering resources are best placed elsewhere, not on a feature that is hardly used.

15 Likes

Ok I first of all, that topic is about simulating removal, not actually removing it. Second, I know how to script fe and I have a game that I’m working on for proof. Third, like I said, the players can’t do anything about it because the developer may be inactive and unable to fix the in-game gear.

The players matter too. There are games that allow gear, and people play them almost daily, I can even link you a few if you don’t believe me. The problem is that it breaks the game for unsuspecting players who just want to have fun on roblox and they end up quitting. FE actually made sense because it both helped the players and the developers by protecting from exploiters but this is just to make something easier for the engineers.

EDIT: Also, if you aren’t aware, the reason I believe this is harmful is because some games and gear use loadlibrary in their scripts to function properly and when this is removed, they won’t work.

3 Likes

The concept is the same and if it was possible, it would be the same as just outright disabling it.

If a developer isn’t active and doesn’t fix their game, then that’s the end of that. It’s not your business what a developer does to their game - whether they want to continue supporting it or not. Play something different or pilot a fan remake project of the game if you’re really passionate about recreating an experience.

No one said players don’t matter, but it seems like my point is sinking right through. These communities are extremely niche. Its not worth expending resources on a feature scarcely used by the greater majority of Roblox (see: games page).

If games break because the developer isn’t maintaining the game, then that’s a completely isolated circumstance that has very little to do with Roblox’s decision to improve the platform. Roblox makes the decision, up to the developer to adapt or drop support for the game’s development.

Even if this update is solely to make engineers life easier, how does that matter? Update your game and leave other developers to update theirs. Engineering (in the context of platform development) and development (itc. game development) are one of the same: making life easier. Engineers remove features that are not being supported or deprecated; developers apply frameworks, libraries and other utilities in their codebase to make development easier and accessible. The concept isn’t any different. You should make things as easy for yourself as you can.


You’ve made this crystal clear. So has OP and so have I across several posts.

5 Likes

It matters because by taking a short cut to “make their lives easier” they are making other people’s lives harder. Gear fighting is my favorite hobby and it has been since I joined and it keeps getting broken due to these updates. You say that we should recreate games if we really care about them, but you wont be able to fully recreate them because theft of scripts is literally not allowed in the terms of service. Neche or not, you should still at least try and help out some of your smaller communities that play your game. Gear isn’t even cheap, I’ve actually spent hundreds of dollars on gear for it just to be broken and not be updated. I probably sound like a broken record at this point but taking shortcuts that cause bigger problems than they solve makes no sense.

4 Likes

Would it be possible to allow some trusted volunteers to update the gears, similarly like some users are able to create UGC items and sell them? If staff moderation time would be an issue, some of the top contributors on this site could moderate the fixed gears.

10 Likes

Absolutely no one suffers from this update except players playing games that, for the fourth time by now, allow arbitrary unmodified gear to be used in their games for whatever reason, which is not a whole lot and not a significant number to justify making a huge commotion about gear scripts breaking.

I’ve stated everything I’ve needed to in several posts now and the OP has made it clear what engineering’s stance on gear and LoadLibrary are. I’m not going to bother discussing this further since it seems, again, that my points at just sinking through and this conversation is derailing the thread.

Gears are akin to hats, just with functionality in them. You can literally treat them the same way.

This isn’t a shortcut and it’s causing no problems. Actively trying to make it a problem isn’t going to go anywhere either. Gear hasn’t been updated for literally a few years and only now because LoadLibrary is going suddenly it’s a supposedly huge problem.

I’ve said my piece. I rest my case. I won’t parrot myself unnecessarily. :slight_smile:

P.S. That GitHub repository isn’t being maintained. The last commit was 2 years ago. Make sure to check dates.

5 Likes