How to make a modules that support from old version (3.2 Beta-14) to latest/newest version (maybe 3.2.6 soon)? Do I need to edit commands.c (old) / l_commands.c (new). Give me an examples if can. Just wanna know.
Universal Modules
Universal Modules
Hello,
How to make a modules that support from old version (3.2 Beta-14) to latest/newest version (maybe 3.2.6 soon)? Do I need to edit commands.c (old) / l_commands.c (new). Give me an examples if can. Just wanna know.
How to make a modules that support from old version (3.2 Beta-14) to latest/newest version (maybe 3.2.6 soon)? Do I need to edit commands.c (old) / l_commands.c (new). Give me an examples if can. Just wanna know.
GreenRoom SEC - Main Coder & CoMaster (http://www.wiramaster.com)
DataServ IRC Services - Main Coder
AirChat Network - Main Coder (http://www.airchat.org)
WebMAS Network - Main Team (http://www.webmas.net)
DataServ IRC Services - Main Coder
AirChat Network - Main Coder (http://www.airchat.org)
WebMAS Network - Main Team (http://www.webmas.net)
You don't need to support beta*... Anyone still runing a beta of unreal 3.2 is an idiot and can easily have his ircd crash, worse, exploited.
As for the 3.2* stable series, usually not too many changes, but you can usually cover them with ifdef's and things like that. Recently we added the UNREAL_VERSION_* ifdefs in include/version.h, but those are quite new, so for older versions you would have to rely on other define's that happened to be introduced or turned on on releasy XYZ, or make some configure system.
Still, older versions are outdated too, so that makes no sense... I would say: support one version below (3.2.3) and current (3.2.4) and up(comming) 3.2.5. This makes sense, since 3.2.2 (the one then not supported) is more than 1.5 years old, and one shouldn't be running such old (server) software.
l_commands / commands has nothing to do with this all, not to mention that there never was a commands.c, and not to mention that you never need to touch these files.
If you don't understand anything from the above, then you are probably not the right C coder, and you should just learn some more first :P.
As for the 3.2* stable series, usually not too many changes, but you can usually cover them with ifdef's and things like that. Recently we added the UNREAL_VERSION_* ifdefs in include/version.h, but those are quite new, so for older versions you would have to rely on other define's that happened to be introduced or turned on on releasy XYZ, or make some configure system.
Still, older versions are outdated too, so that makes no sense... I would say: support one version below (3.2.3) and current (3.2.4) and up(comming) 3.2.5. This makes sense, since 3.2.2 (the one then not supported) is more than 1.5 years old, and one shouldn't be running such old (server) software.
l_commands / commands has nothing to do with this all, not to mention that there never was a commands.c, and not to mention that you never need to touch these files.
If you don't understand anything from the above, then you are probably not the right C coder, and you should just learn some more first :P.
Im understand about it. Thanks for answering my question, pal 
GreenRoom SEC - Main Coder & CoMaster (http://www.wiramaster.com)
DataServ IRC Services - Main Coder
AirChat Network - Main Coder (http://www.airchat.org)
WebMAS Network - Main Team (http://www.webmas.net)
DataServ IRC Services - Main Coder
AirChat Network - Main Coder (http://www.airchat.org)
WebMAS Network - Main Team (http://www.webmas.net)