• Content Count

  • Joined

  • Last visited

Community Reputation

462 Excellent

About ago

  • Rank

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. And to follow up from the PM: Java 10 is crashing because its missing the JavaFX libraries. This exactly what I was expecting. WU is not prepared to run on Java 10. Someone with some skill can probably get it to run by adding the missing libraries to Java or WU. But I don't plan to sink any time into tinkering how to get WU to run in Java 10. Hint: Search for how to get JavaFX on Java 10
  2. [Runtime] OverrideDefaultJavaPath=true JavaPath=C:\Program Files\Java\jre1.8.0_231\bin\server [Memory] InitialHeap=512m MaxHeapSize=2048m [VMParams] JvmParam0=-XX:+AggressiveOpts JavaPath must point to the directory with jvm.dll or on linux I haven't tested it with Java 10, just the Java 8 i had installed anyway.
  3. LaunchConfig.ini allows you to override the Java path [Runtime] OverrideDefaultJavaPath=false JavaPath= patcher.bat uses the Java that is shipped to every WU user by default. I don't think there is any hard dependency on Java 8 in the patcher. So you can replace the path in patcher.bat. Going to Java 10 or 11 may break some mods however. At least the scriptrunner (server) mod and anything that depends on it may break because Oracle decided to deprecated the integrated Javascript runtime. I'd advise to first try to get vanilla WU to work by adjusting the path in LaunchConfig.ini. If this works properly you can try to get it to run with the modloader.
  4. By default the version is read from the Implementation-Version field from the jar manifest. But you can override the getVersion() method on the WurmMod class and return any version string you like.
  5. I'm aware of the issue but did not have a chance to look into it yet.
  6. contains the modlauncher and all mod but it does not contain any .properties or .config files. This is to update the mods but will not activate any that has not been active before. If you want to activate one of the mods it's best to download the mod only packge (e.g. Those contain the .properties file for mod and activates the mod. Documentation for the mods is at
  7. When did this happen, was it critical to the server/cluster? I think the first server poll will actually run before the server startup was completed.
  8. Version 0.43 modloader Update to Wurm Unlimited
  9. This is a pre-release intended to be used with the WurmUnlimited Beta Version 0.43-beta1 modloader Update to Wurm Unlimited [bdew]
  10. Best way is probably to run modlauncher.bat The other option is to patch WurmServerLauncher. Run patcher.bat. This will modifiy server.jar and create a modified WurmServerLauncher-patched.exe. You can run this or copy WurmServerLauncher-patched.exe over WurmServerLauncher.exe and run WurmServerLauncher.exe.
  11. Version 0.42 modloader fix wildcard glob (*.jar) classpath entries
  12. A recent fix required to check for named jars first. This seems to break the wildcard lookup. I'll put a fix out tonight.
  13. It's essentially the demo case for the CreatureMod and has been superseeded by CreatureMod.
  14. I went a different path. Since the Loader is already a classloader I simply added the proper getResource/findResource/findResources methods. Version 0.41 modloader ItemIdParser and CreatureTemplateParser can read ids from the modsupport db after the server has started Fix resource loading and callback api from shared class loader [#51]
  15. [RELEASED] Client mod loader

    Make sure that IP-address sent is the one of the server and reachable from the client. Also make sure that the httpserver port is open in the firewall. You can copy the URL from the console window and try to download it in your web browser. This should make troubleshooting a lot easier.