- All extra addons for gmod update#
- All extra addons for gmod mods#
- All extra addons for gmod crack#
What do you mean ? We can make it for gmod only.User chose addons that they wanna use, we have no control over that, no need to support specific addons.I guess you have some misconceptions about my idea.
I'm sure that a lot of what you're looking to do could be done with this script, I'd be happy to take a crack at helping you add the features you need to it and sharing thanks for your attention. I have a simple script for my Insurgency servers that clones out a bunch of repos, rsyncs some maps, and does some other cleanup afterwards, all driven by a config manifest. Once we have a clear idea exactly what you're looking to do, we can look at creating a tool. I want to be able to push changes back upstream as well, or branch my own versions.
I want to be able to update and pull all repos, or just individual ones. I want to be able to add repos to the file and have the tool clone them. I want to be able to create a list of Git repos with the local paths they should be installed in. That way, we know what we want to do, and then can build the tool to the desired actions, not just go in blind. My suggestion here would be to clearly state what you want, so we can define a specification for the script. This is a big problem I ignored in my Insurgency server sync script that does something like this, it caused me quite a headache.
How will we handle authentication, i.e. A lot of projects are still in SVN, Mercurial, or (shudder) CVS as well. This will require a lot of new dependencies (Git primarily) that will need to be taken care of in the setup phase. git) the directory and use all those repos? So, will the script use a simple manifest file, or will it just $(find -type d -name. Inventory and tracking of the repos (if we don't keep a centralized list) would need to be mapped out. Granularity for the server admins needs to be a big concern here, so we need to fully understand how the update and use of these repos works across the games we will support. Not everyone will have the same addons, or want to get the latest versions of all pieces. This will quickly become prohibitive and out of date. All games will now not only need game data and scripts, but also a registry of mods and addons that we support. Otherwise, we need to consider a few big issues with this: My thinking here is that an external tool might be a better idea, especially given how much extra functionality this will need to work robustly. And it could be a step forward to adding optional and very used and useful addons to gmod that would be managed by LGSM. But it could also apply to ulx/ulib, utime, and uclip, which would be very cool, as they are serious developers that update their addons only when it's really required. I'm thinking about mainly 2 addons that are Adv Dupe 2, and ACF that are only found onto github. Or because a guy welded the head of a ragdoll to a high enough skymap. Everyone is used to a server crashing because of a coded by feet duplicator tool. Gmod server admins AND players usually prefer functionalities over stability. Many admins are still using github addons, as some of them have more functionalities or correct some more bugs. The game engine doesn't even support multi thread anymore (even if settings seems to allow it) because it breaks the lua engine synchronization and makes the game unstable ! I can guarantee you that it won't ever be stable. Haha ! Nothing is ever stable with gmod ! I'm saying that because i started playing before it was even available on steam.
0 kommentar(er)
