germathought.blogg.se

How to create sourcemod plugins
How to create sourcemod plugins








how to create sourcemod plugins how to create sourcemod plugins
  1. #How to create sourcemod plugins install
  2. #How to create sourcemod plugins update
  3. #How to create sourcemod plugins windows

#How to create sourcemod plugins windows

You can ask me, but I need server* and engine* binary files for windows and linux v34 (server_srv.so/dll.) You can try to find the signatures by yourself using the youtube instruction or ask somebody to do it for you. The last step is quite simple, at least for me :) it's described in "Extra information" in my previous post. And of course you can try to use my instruction for ambuild (previous message) if Makefile doesn't work for you. but you can use the MakeFile from the extension archive, it worked for me just fine a few years ago. not sure if ambuild is competable with v34 and old SDKs. It does exactly what you need, but for other functions, which you will have to replace to the ones from your plugin.

how to create sourcemod plugins

it wouldn't take much time if you good at C++.ġ) Write an extenson with all the DETOUR's, VPHooks and whatever else you need.Ģ) Build it against actual (for you) versions of SM and MM and your engine versionįor the first step try to build this extension: I may assure you that it's hardly possible for you to rewrite this extension for old versions of MM and SM, couse it's huge and not well documented. but, as you have it written, it is a lot easier to correct the signatures, of course if you have DHook for you version of server. It's a lot more complicated to write such plugin.

#How to create sourcemod plugins install

don't forget to install gcc, g++ and the other shit that is required for everything to work. Yes, you can ask your questions here, And No, I won't answer PM questions. If you have problems with libstdc++, read this topic: ) If you want the compiler to ignore some bad warnings add this (I wouldn't recommend it though):ĪMBuildScript -> cxx.cxxflags -> '-Wno-error', (don't forget the comma) Ĭomment the extension path here: AMBuildScript -> BuildScripts to remove or disable some of the extensions If you get a message that one of the sdk headers is missing, add it's dir here If you ran into problems, you can ask your questions here: Read the information below if you still have problems or questions. a useful video about signing by ProdigySim: The relative gamedata are located here: "addons/sourcemod/gamedata"

#How to create sourcemod plugins update

Update the extension signatures and offsets if necesarry. it has all the *.cpp files of the project,Īnd the file name of the extension isn't "". If it doesn't work, make sure that the AMBuilder is correct, i.e. To set another game, correct this part of the command "-sdks css" All the available game types are here: AMBuildScript -> PossibleSDKs. Make your choose, whether you need Release or Debug version: From now on you may follow the "Rebuilding extensions" block as well. You can skip this step if the sources have a valid AMBuilder file.Īdd your extension to the ambuild config: *SDK/sourcemod/AMBuildScript this way: "cstrike" with whatever name you need and save the file. Open it and add all the *.cpp and *.c files into the "project.sources" block, and remove the old ones. "cstrike" extension has an AMBuilder script: "Extension/AMBuilder", copy it into yours extension folder, You can see there are other extensions at "*SDK/sourcemod/extensions". If you have problems, look at the example extensions located at this folder.įllow step 3 if your extension doesn't have ambuild configurations, omit it otherwise Put your extensions into this folder: *SDK/sourcemod/extensions "ambuild", "hl2sdk-*", "sourcemod", "mmsource-*" and may be "mysql-*" "/home/d/SDK/" for instance.Īt this moment you have these folders in your SDK directory: Run CMD and set current directory for the SDK. Omit this instruction, unless you need to install/reinstall the source SDK environment = Setting up the Environment and building extensions = Open CMD and set current directory to this: "/home/d/SDK/sourcemod/build"Ĭopy the result "*.so" file to this folder: "addons/sourcemod/extensions" Replace AMBuildScript file with a newer one The result should look AS this "/home/d/SDK/sourcemod/extensions/" Move "extensions" to "/home/d/SDK/sourcemod/" Omit this instruction, unless you have the SDK environment set up Ok, what I wonna tell you is that you should do it by yourself and it's your lucky day, couse I've got a special instruction for you.įollow these steps: 1 and 4 (omite the others, the others are for SMMM extensions) And I'm definitely not ready to keep it and rebuild SM after each update. At the moment I have no *unix system, have no time to set it up from scratch. I used to use VmWare Workstation and it consumed about 20GB on my hard drive. And it's good if you work in *unix environment couse it won't take that much time to ajust everithing, otherwise you have to have some sort of "virtual system" and it'll definitely require space on your hard drive. Each new SM or MM version will require the extension to be recompiled. Wow, guys your avatars and styles of writing are so much alike, are you brothers? :)










How to create sourcemod plugins