[bigdaddy424]

• Description
  This plugin will check if AMX Mod X is running the latest build
• Cvars
  update_notice - (default "1.9") amxx version to look after to
  Note that it can only follow updates for 1.9 and 1.10 versions.
• Modules
  Requires < sockets > & < nvault >
• Install
  1. Works on AMXX 1.8.1
  2. Drag amxx_update_notice.sma to amxmodx/scripting folder
  3. Click "Get Plugin" and drag amxx_update_notice.amxx to amxmodx/plugins folder
  4. Type amxx_update_notice.amxx in amxmodx/configs/plugins.ini file
  5. Type update_notice "<AMXX_VERISON>" in amxmodx/configs/amxx.cfg file
• Credits
  fysiks - version comparisment
• Additional information
  Instead of sending a request to check latest amxx version at amxmodx website every map change, it will only do it once a day and will save that value with today's date assigned as the key.
  If a new version is released, the plugin will alert all admins 5 minutes after the map change.
• Image
  
  

[fysiks]

No need to give trivial instructions for installing a plugin that is identical to installing all other plugins (FYI, the .sma file is not required to be on the server for the plugin to run). Also, using the compile date for the plugin version is a bad idea and defeats the entire purpose of version numbers.

That URL doesn't work for any version before 1.9 so that should probably be noted (and makes it pointless to run on anything older than the latest 1.9 version).

Should also clarify that the cvar can only be the major and minor version.

Each section of the version number should be compared independently as integers. Doing it with the string method will have issues in certain scenarios.

[bigdaddy424]

i've made some changes and did the version comparison using integers and not strings since it makes more sense. the only reason thats compatible with 1.8.1 is so its the forum takes care of compiling the plugin for you

[fysiks]

Mashing all the numbers together is not the proper way to compare versions and can cause incorrect results in some situations. However, you might be able to get away with it here assuming that the build number will never reset.

The proper way is to compare the components as integers independently. You can find an example in a few different programming languages here. C++ is the closest to Pawn.

[bigdaddy424]

Credited you for that, thanks