[WIP/ADMIN] Bukkit Plugin Watcher V. 0.9.4.45 Beta - GUI For Keeping An Eye On Plugin Threads

Discussion in 'Bukkit Tools' started by cyberdude, Jul 23, 2011.

Thread Status:
Not open for further replies.
  1. Offline

    cyberdude

    Canceled so far! Can not work with BukkitDev in it's current form. If BukkitDev gets updated and accomodate the changes asked by the community, I might be able to start this up again and see if I can support BukkitDev. Until that I won't provide new updates, it's just not worth putting effort into this before BukkitDev has been sorted. In the mean time check my other plugins in my signature.
    Download Link (DropBox) - Always the newest version​
    Fixed (IMPORTANT BEFORE UPDATE from lower than 0.9.3.67 delete file pluginslist.txt or else it will crash)

    Tired of checking 10's or 100's of URLs to check up on a plugin, to find out it still hasn't been updated for the lastet Bukkit build.
    Here is Bukkit Plugin Watcher to the rescue.

    [​IMG]

    Fire it up, paste the URLs to your favorite plugins, and your set.

    Old thread was closed by the Bukkit Team because it was putting too much load on the bukkit servers by scraping the threads, now the application is rewritten and now uses the plugins.bukkit.org list, and caches it for 24 hours. Therefor the application no longer adds any unnecessary load on the servers.

    Features:
    • Auto update on start.
    • Extracts various data from Titles of inserted thread urls
    • Sortable
    • Marks fields with light yellow when they are updated with new information
    • Import URL list from file
    • Import/Export.
    • Auto extract bukkit build
    • Find installed plugins and versions
    • Only supports plugins in Bukkit Plugins List (plugins.bukkit.org)
    How to use/Description:
    • Start it (Obviously), enter new urls by clicking in URL column of the bottom empty row.
    • In options set path to bukkit jar file (if running on the same computer you use this application)
    • Row will automatically be updated with extracted data, and saved.
    • Plugins can be deleted by clicking in the left (empty) column where the arrow is, so the entire row is marked, press delete.
    • When the application is started it will load the stored data, and start updating (If there are many rows, you will notice that GUI will freeze during this update (which takes a few seconds depending on the hardware, and internet speed available).
    • Clicking the name will open up your default browser pointing the the thread url.
    • Only three columns are editable, URL and Manual Compat and Installed.
    • Compat is short for Compatibility.
    • Enter your current Bukkit Version (Or the one you want to compare against, if you are waiting for plugins to become available for the next Bukkit build before you update, or auto detect if setup to do that) in the "Bukkit Version" field, enter the Bukkit Build that you think should still support most plugins. In the default case, we know plugins working on 818 are most likely going to work on 935 because no major breakage have been going on here. This is an assumption, some plugins might work, some might not, if a plugin is only supporting a version lower than this, it's likely not working, might be though.
    • The Bukkit Compat column is checked when the Bukkit build that the plugin supports matched the Bukkit Version you supplied. If it is higher or in between the Bukkit Version and the Compat version it will be set as indecisive, meaning it might work, it might not. If it is unchecked, the plugin supports only a version lower than the Compat build that was set. The plugin is most likely not supported.
    • The Manual Compat can be manually set (Checked, indecisive, unchecked), which basically overrides the Bukkit Compat, so if a plugin is flagged as Indecisive, you can here set it to Checked if you know it works, or unchecked if you know it doesn't work.
    • The Compat column basically uses the two columns before to set it's value. If the Manual Compat is Checked or Unchecked it will use this value, of it's Indecisive it will use the value of Bukkit Compat.
    • The Installed Dropdown contains all plugins detected as installed, if will be auto filled by best effort, if it doesn't auto detect you can manually select a plugin that corresponds.
    Future:
    • Tray icon, run i background checking once in a while, popup/inform when something updated,
    • maybe select what plugins to watch and inform about (If you are waiting for a certain plugin to be updated)
    • I have been thinking about extracting download link, as to easily (or automatic) download plugins (perhaps on certain criteria). But I'm not sure this is feasable, since there are so many different ways the download link can look and be hosted at, that I'm not sure I can find a way to reliably extract that.
    • Auto update Compat build number from a webservice (that I provide) that will aim to be as correct as possible)
    • Somehow connect to a bukkit installation remotely. I'm thinking about adding support for JSONAPI
    • Others, write your ideas, and we will se where that will take us.
    Known Bugs:
    • Everything is based on a "Best Effort" practice, so everything depends on the information the plugin authors writes in the thread title, and the information in the plugins.yml file in the plugin. If the plugins.yml contains wrong version information I can't do much about it. The application uses the information it is provided.
    • Some threads can't be extracted properly yet, the reason being I am using a very sophisticated regular expression to extract the data, however there are so many ways people write their thread title that I can't support them all in one go, I will write a new method that will better cope with all plugins. I have rewritten the method, and supports very close to 100%
    • Other bugs might occur.
    Changelog:
    • 0.9 Beta: First release
    • 0.9.1.74 Beta
      • Improved extraction of data (A lot)
      • Menu
      • Import/export
      • Better saving
      • Some error handling
      • Handle empty lines(urls), are now counted as delete row.
    • 0.9.2.12
      • Auto detect bukkit (If pointed to location)
      • Options
      • Custom color for change mark
      • Store change marks, and ability to clear
      • Detect plugins installed
      • Relate plugins installed with watched plugins
      • Status(And icon) to show Error, Up to date, update available and Not installed
      • Use plugins.bukkit.org to extract thread titles from.
      • Faster
    • 0.9.2.13
      • Fixed 2 small bugs
    • 0.9.3.67
      • Rewrote scraping to support Plugin List "official API" (Thanks to the bukkit team and lukegb for giving us an official way to get this data)
      • Fixed correct sorting of numbers (bukkit build version)
      • Plugin threads that are inserted are now checked against installed plugins and autodetected when inserted. (Can only detect against plugins already present when application is launced)
      • Fixed the bug that was mentioned as the last known bug (The application extracts the.........), it turns out it happened when files were readonly.
      • If pluginslist.txt is deleted it will force a new recache of Plugin List, please don't use just for fun, to force a recache, there is a reason why I'm caching the scrape.
    • 0.9.4.43
      • Rewrote and almost perfected extraction of data from thread titles, now supports almost 100% of all plugins.
      • Supports Plugin submissions, when they follow submission guidelines
    • 0.9.4.45
      • Fixed some bugs when saving, which caused categories to duplicate.
    Technical:
    • Data stored in stored.xml file in the path of the file.
    • Requires .Net 4.0.
    • Application is scraping plugins.bukkit.org and storing a cache for 24 hours. Using this it can get the thread title using the forum url.
    Enjoy and comment

    When reporting bugs, please report how to reproduce and post crash log, also check that you are running the latest version.

    Download Link (DropBox) - Always the newest version

    @Birdie @blaize9 @BrightNail @MCManager @Imper1um @dragonhib @Taranis01 @Blechbuexse
    Pointing you all to the new thread

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: May 17, 2016
    MCManager and Taranis01 like this.
  2. Offline

    MCManager

  3. Offline

    cyberdude

    It was closed, because it put too much unnecessary load on the bukkit servers, because it scraped each thread. Now I've done it another way. I haven't heard from the team yet if I could get my old thread back, but couldn't wait any longer, so released now in a new thread.
     
  4. Offline

    Taranis01

    that means, Plugins in the Submissions-Categorie doesnt work? :(
     
  5. Offline

    MCManager

    no... they are not in that list :/
     
  6. Offline

    cyberdude

    Correct, unfortunately this is the only way I can do it that will also make the bukkit team happy. The old method puts too much load on the bukkit servers that are already under a large pressure.
     
  7. Offline

    Taranis01

    damn :(

    okey, i just imported the old .xml file and then saved it. But after pressing the manual Update BukkitPluginWatcher crashed (and crashed itself after restart too). I then deleted pluginlist.txt and stored.xml and tried starting again: "Unhandled exception...." (Could not finde file: ....\pluginlist.txt). I pressed Continue but got another exception (2 times) after that: "Object reference not set to an instance of an object". I tried the importing again and again the "Object reference..."-Error 2 times.
    edit: and after that i only where abel to close it using the taskmanager because clicking on the X just makes another exception.

    I guess i have to import the plugins manually? ^^

    edit: just asking...what was the "old way"? I guess looking for the Title?
    Isn't the URL of the plugin the same as the Title in the end?
     
  8. Offline

    cyberdude

    I wrote a PM to you.
    I am not really sure why it crashed the first time. You should however not need to import the old .xml file if you just put it in the same location as the new version (And keep the name stored.xml).


    Funny thing is I just added this to known bugs just before you wrote:
    - If you delete the pluginslist.txt file generated the application will properly crash, until 24 hours have passed. The application remembers when the last scrape occured and stores the information in this file. You can't cheat the application by deleting this file. So don't do it.
     
  9. Offline

    Taranis01

    copying the old .xml into the BPW-folder causes immediately crash of BPW (<- BukkitPluginWatcher ^^) when starting :(
     
  10. Offline

    cyberdude

    Can you post the crash message? I did spend time making sure the old .xml would be handled in the new, because I've change a lot. I might have missed a tiny thing.

    Edit:
    I just tried with a stored.xml file from the first version I released, and I didn't crash for me. I can't reproduce, so I don't know whats wrong. I would very much like if you could post your old .xml file, then I can try it out.
    However I'm sure I'll be doing too much work on backwards compatibility, only a few people ever used the first version, and hopefully those people can start over again. If it's too much trouble I'll see what I can do to work this out. If not then just start from scratch. Send me the .xml file and I'll take a look.
     
  11. Offline

    Taranis01

    unfortantly its not an error like them before. It looks like BPW is updating (after start) and then it crashes:
    Code:
    Problemsignatur:
      Problemereignisname:    CLR20r3
      Problemsignatur 01:    bukkitpluginwatcher.exe
      Problemsignatur 02:    0.9.2.12
      Problemsignatur 03:    4e2adc07
      Problemsignatur 04:    mscorlib
      Problemsignatur 05:    4.0.0.0
      Problemsignatur 06:    4da3fe76
      Problemsignatur 07:    e4c
      Problemsignatur 08:    5a
      Problemsignatur 09:    System.FormatException
      Betriebsystemversion:    6.1.7600.2.0.0.256.1
      Gebietsschema-ID:    1031
      Zusatzinformation 1:    0a9e
      Zusatzinformation 2:    0a9e372d3b4ad19135b953a78882e789
      Zusatzinformation 3:    0a9e
      Zusatzinformation 4:    0a9e372d3b4ad19135b953a78882e789
    
    i attached my stroed.xml
     

    Attached Files:

  12. Offline

    cyberdude

    I just tried your stored.xml, and it doesn't crash, so I expect you didn't notice that I had released an updated version a few moments after I opened this thread where I fixed 2 minor bugs. It seems that one of these bugs is causing your crash. So the new version 0.9.2.13 should work and fix your crash.
     
    Taranis01 likes this.
  13. Offline

    Taranis01

  14. Offline

    cyberdude

    Thank you, I will check up on that.
    I don't support the other tags in brackets [], such as [PERMISSIONS], [NETHERRACK], [4.6], [All Economy], [5,2].

    I will fix up the extraction of data later. I am thinking about adding ALL plugins to my list while developing, and making sure I support all current plugins.

    I think I forgot to answer this question.
    No the url is not the same as the thread title. Based on the plugin submission guidelines Bukkit version has to be written in brackets [1000], so I know bukkit versions is written this way. In the thread URL the brackets are missing, thus I can't reliably guess what the number is for. 1000 or 953 might mean anything in the thread url, it could be part of the plugin version number or something similar. I can't properly distinguish the category because of this also. Based on the thread url how is the application supposed to know whether "admin" is part of the application name or the category, as an example you can look at this thread url and title, is this application named "Admin Bukkit Plugin Watcher" or "Bukkit Plugin Watcher".
    The same goes for differentiating between the name and the "description". Guideline is to write the name, version followed by a dash and then the description. E.g. "Plugin v.1,3 - Some description for the plugin". Because all spaces are converted to a dash (-) and apparently if more dashes are following each other they are removed. So the example turns into "plugin-v.1.3-some-description". Thus I don't have a reliable way to determine what is the plugin name and what is short description.
    Some plugins doesn't provide version number in thread title/url such as HelpMeAdvanced (and others) where the url turns into e.g. "admn-misc-helpmeadvanced-a-more-advanced-help-me-system-733-928". As you can sure the application has no chance of knowing what the plugin is called. Is it "helpmeadvanced"? Or is it "helpmeadvanced a more" or what is it? The application doesn't have any AI to use human nature skills to detect what the name is and what is description. In this particular case the name is 1 word, but this isn't the case for all plugins.
    And lastly using the thread urls all case is lost because all text is converted to lowercase. In the case of helpmeadvanced, the plugin name is really "HelpMeAdvanced".
    Therefore I can't reliably use the thread url for extracting the information.

    The old way was to fetch the html for the thread url, and extract the thread title that way, doing this for every plugin url, basically putting the same load on the bukkit servers as if one person was viewing the thread page for every url, one person easily going 20-30 or even 60-70 thread urls. I even optimized the application to do this fetching of data as fast as possible, taking (on my connection and computer) around 30 seconds to scrape the data from 70 threads, which puts a lot of load on the bukkit servers, scaling this with the idea that many people would be using the application would put a HELL of a lot of load on the servers, which in hindsight is a bad idea ;).
    Now I fetch the data from plugins.bukkit.org and store this cached for 24 hours (So if you open the application again, or enters a new plugin url, it will NOT reconnect to plugins.bukkit.org, but instead use it's own stored cache of the list until 24 hours have passed since last update). I do some other magic in here, because the data I get from plugins.bukkit.org doesn't contain the exact thread urls, but rather just thread id's.
    This means that the application will now only make a request on the bukkit servers at max once every 24 hours. The downside is that now I can only support the plugins in the plugin list, not plugin submission or plugins thrown into the inactive forum.

    I hope this clears your question :)

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: May 17, 2016
  15. Offline

    tha d0ctor

    Something seems to be wrong with this program

    I get errors on everything, evne when I try to X out the program I get an error and I can't even close the program...
     
  16. Offline

    blaize9

    Thanks for the updates and the new thread =D
     
  17. Offline

    Taranis01

    i had that problem before too.
    delete C:\Users\<UserName>\AppData\Local\BukkitPluginWatcher and try it again. If u get this problem again download BPW (BukkitPluginWatcher) again, cyberdude fixed some bugs shortly after posting this thread
     
  18. Offline

    cyberdude

    Can you post crash/error log, error message? And check that you are running latest version 0.9.2.13?
     
  19. Offline

    microskies

    Do you think you would be able to add support for remote servers / tell me how I could use this with my hosted server?
     
  20. Offline

    cyberdude

    Currently you can not use this with your hosted server (unless you have VPN connection to it, and can share the bukkit folder on network with your self). I've been thinking about creating a "remoting" plugin for bukkit, or maybe interface with one of the existing ones. The interface would require that it can return the Bukkit build version (Or version string) and installed plugins + version number. If you know of any such remoting plugin/server manager that allow these functionality then I would like to know and I might look into it.
     
  21. Offline

    Taranis01

    u know, i had the same problem (but not anymore :) ). Its the "Object reference not set to an instance of an object" error.

    okey, just started BPW and got this Unhandled exception: "Invalid JSON primitive: ."
    Show Spoiler
    See the end of this message for details on invoking
    just-in-time (JIT) debugging instead of this dialog box.

    ************** Exception Text **************
    System.ArgumentException: Invalid JSON primitive: .
    at System.Web.Script.Serialization.JavaScriptObjectDeserializer.DeserializePrimitiveObject()
    at System.Web.Script.Serialization.JavaScriptObjectDeserializer.DeserializeInternal(Int32 depth)
    at System.Web.Script.Serialization.JavaScriptObjectDeserializer.BasicDeserialize(String input, Int32 depthLimit, JavaScriptSerializer serializer)
    at System.Web.Script.Serialization.JavaScriptSerializer.Deserialize(JavaScriptSerializer serializer, String input, Type type, Int32 depthLimit)
    at System.Web.Script.Serialization.JavaScriptSerializer.Deserialize[T](String input)
    at BukkitPluginWatcher.BukkitPluginListScraper.scrape()
    at BukkitPluginWatcher.frmMain.Form1_Load(Object snder, EventArgs e)
    at System.Windows.Forms.Form.OnLoad(EventArgs e)
    at System.Windows.Forms.Form.OnCreateControl()
    at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
    at System.Windows.Forms.Control.CreateControl()
    at System.Windows.Forms.Control.WmShowWindow(Message& m)
    at System.Windows.Forms.Control.WndProc(Message& m)
    at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
    at System.Windows.Forms.Form.WmShowWindow(Message& m)
    at System.Windows.Forms.Form.WndProc(Message& m)
    at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
    at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
    at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


    ************** Loaded Assemblies **************
    mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.235 (RTMGDR.030319-2300)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
    ----------------------------------------
    BukkitPluginWatcher
    Assembly Version: 0.9.2.13
    Win32 Version: 0.9.2.13
    CodeBase: file:///C:/Users/Taranis/Desktop/BukkitPluginWatcher2/BukkitPluginWatcher.exe
    ----------------------------------------
    System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.235 built by: RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
    ----------------------------------------
    System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
    ----------------------------------------
    System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.232 built by: RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
    ----------------------------------------
    System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
    ----------------------------------------
    System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
    ----------------------------------------
    4oztafv0
    Assembly Version: 0.9.2.13
    Win32 Version: 4.0.30319.232 built by: RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
    ----------------------------------------
    g5tzppab
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.232 built by: RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
    ----------------------------------------
    System.Web.Extensions
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.206
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Web.Extensions/v4.0_4.0.0.0__31bf3856ad364e35/System.Web.Extensions.dll
    ----------------------------------------
    System.Web
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.206 built by: RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Web/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Web.dll
    ----------------------------------------
    System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
    ----------------------------------------

    ************** JIT Debugging **************
    To enable just-in-time (JIT) debugging, the .config file for this
    application or computer (machine.config) must have the
    jitDebugging value set in the system.windows.forms section.
    The application must also be compiled with debugging
    enabled.

    For example:

    <configuration>
    <system.windows.forms jitDebugging="true" />
    </configuration>

    When JIT debugging is enabled, any unhandled exception
    will be sent to the JIT debugger registered on the computer
    rather than be handled by this dialog box.

    I pressed Continue and now my whole Pluginlist is gone! (i only have an older version saved somewhere else)
    Then i tried to close BPW and again the exception:
    "Object reference not set to an instance of an object"
    Show Spoiler
    See the end of this message for details on invoking
    just-in-time (JIT) debugging instead of this dialog box.

    ************** Exception Text **************
    System.NullReferenceException: Object reference not set to an instance of an object.
    at BukkitPluginWatcher.frmMain.save()
    at BukkitPluginWatcher.frmMain.Form1_FormClosing(Object sender, FormClosingEventArgs e)
    at System.Windows.Forms.Form.OnFormClosing(FormClosingEventArgs e)
    at System.Windows.Forms.Form.WmClose(Message& m)
    at System.Windows.Forms.Form.WndProc(Message& m)
    at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
    at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
    at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


    ************** Loaded Assemblies **************
    mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.235 (RTMGDR.030319-2300)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
    ----------------------------------------
    BukkitPluginWatcher
    Assembly Version: 0.9.2.13
    Win32 Version: 0.9.2.13
    CodeBase: file:///C:/Users/Taranis/Desktop/BukkitPluginWatcher2/BukkitPluginWatcher.exe
    ----------------------------------------
    System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.235 built by: RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
    ----------------------------------------
    System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
    ----------------------------------------
    System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.232 built by: RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
    ----------------------------------------
    System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
    ----------------------------------------
    System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
    ----------------------------------------
    njz5nkib
    Assembly Version: 0.9.2.13
    Win32 Version: 4.0.30319.232 built by: RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
    ----------------------------------------
    kqeg10wu
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.232 built by: RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
    ----------------------------------------
    System.Web.Extensions
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.206
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Web.Extensions/v4.0_4.0.0.0__31bf3856ad364e35/System.Web.Extensions.dll
    ----------------------------------------
    System.Web
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.206 built by: RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Web/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Web.dll
    ----------------------------------------
    System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
    ----------------------------------------

    ************** JIT Debugging **************
    To enable just-in-time (JIT) debugging, the .config file for this
    application or computer (machine.config) must have the
    jitDebugging value set in the system.windows.forms section.
    The application must also be compiled with debugging
    enabled.

    For example:

    <configuration>
    <system.windows.forms jitDebugging="true" />
    </configuration>

    When JIT debugging is enabled, any unhandled exception
    will be sent to the JIT debugger registered on the computer
    rather than be handled by this dialog box.
    (and im only able to close BPW using Taskmanager)

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: May 17, 2016
  22. Offline

    cyberdude

    @Taranis01
    Top of post specifies that it's currently out of order :).. Last night bukkit team made a major update on plugins.bukkit.org, I have update and fixed it but not uploaded yet because I'm waiting for a response from the bukkit team about something that might make things a bit easier.
     
  23. Offline

    JoshuaBehrens

    I've done a lot using .Net-Framework, but you don't need .Net 4 to do this. Make it more useable for those who don't have XP< or not Windows. .Net-Framework 2 is more than you need, but lower is almost impossible to compile on.
     
  24. Offline

    cyberdude

    The first version was using Parallel to scrape Thread url as fast as possible. My current version also uses Parallel to scrape all page of the Plugin List, but hoping to get an answer from the Bukkit team soon that will mean I won't be needing Parallel. Yes I could thread it manually, but I'm short of spare time already. If I get the response from the bukkit team I'm looking for then I'll try compiling it again as low as I can. But currently I can't go lower than 3.5..
     
  25. Offline

    JoshuaBehrens

    So go to 3.5. 4 is not working properly on XP ;)
     
  26. Offline

    cyberdude

  27. Offline

    cyberdude

    @Birdie @blaize9 @BrightNail @MCManager @Imper1um @dragonhib @Taranis01@Blechbuexse @tha d0ctor
    New update supporting almost 100% plugins, including submissions.
    Some stats:

    Out of 1784 plugin threads:
    2 - Where it can't distinguish between Plugin name and plugin description
    2 - Where it can't extract Plugin names
    2 - Where Version is detected as 3co (which it shouldn't)
    36 - Where there are no version detected (because no version information is present in the Thread title)

    So 6 threads out of 1784 that it can't properly extract the data from is a success rate of 99,66%

    I find this to be a very high success rate based on the fact that thread titles are written in so many different ways.
    I hope you like this update, I've spent as much time on this last update as I've spent on the entire application up until.
    It has been tested against the entire list of plugins available from the Plugins List.
     
    Taranis01 likes this.
  28. Offline

    Taranis01

    @cyberdude
    great update, it works fine for me :)
    the "Update all" Feature marks the Category-part from all Plugins as updated and duplicates the Category so that i now have something like "Fun, Mech, Fun, Mech, Fun, Mech" ^^
     
  29. Offline

    cyberdude

    Yeah, I noticed, and fixed it in my next version. I have some other stuff going on in the next update, and some of it is only part finished, so I can't release something with some stuff only half working. Will release soon though, hopefully in the weekend.
    When you get the next update it will fix the categories on all the plugins. Sorry for the inconvenience.
    Also found some problems with version comparison. Currently I'm using a built in version in .Net, but it requires the version as X.Y, so when a plugin uses version numbers whole number, then it won't work.
     
    Taranis01 likes this.
  30. Offline

    Taranis01

    @cyberdude
    i also would suggest, that the settings are saved somewhere, so they're not lost after replacing the .exe with a new version.
    thank you for great work :)
     
Thread Status:
Not open for further replies.

Share This Page