• Content Count

  • Joined

  • Last visited

Community Reputation

464 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. Version 2.6.1 newer horse colors were missing in traits window
  2. Ok, checked a horse with "regular bay" trait. (Ebony wand -> Traits). It shows with the correct texture and the overlay shows: The model name specifies which model and texture to load. The model name is correct (for a regular bay horse). From your image I can see the client loads the model and texture from graphics.jar, not from the creaturemods graphics pack. Could the download of the pack be broken or maybe incomplete? The console would show which packs are loaded. Also the examine message shows the correct colors for me: EDIT: with changed colors I meant that horses with trait 33 would have shown as custom color "piebald" before but will now show with the unmodded color "appaloosa". The trait numbers don't change but the color associated with the trait numbers have changed. I just noticed that the "new" unmodded colors do not show in the Traits window. I'll fix that
  3. No. The original author does not update the mod anymore and I'm basicly just fixing bugs in the code. The horse model in the mod is probably too old to support visible equipment but I don't have the skill nor the time to update it with the models from the vanilla horses.
  4. Version 2.6 Fix color traits The custom horse traits had to be moved again. This means the colors of your horse may have changed, sorry about that. is required for the fixes for corpse textures and the "Traits" GM dialog.
  5. Version 0.44.1 modloader Fix horse traits and custom creature colors Fix corpse colors
  6. [RELEASED] Client mod loader

    Version 0.14 serverpacks add ability to reference local pack in overrides (bdew) This lets you write something like that in mappings.txt model.transports.medium.wagon.molr=~graphics.jar/transports/Wagon_main.wom?tentMat.texture=~[local]/wagon_SA.png Which will load wagon model from graphics.jar but override one of the textures from the current pack. [local] will be replaced by the name of the pack at runtime.
  7. [RELEASED] Client mod loader Version 0.13 serverpacks Fix client lockup when trying to reference a non-existing cross-pack resource (bdew)
  8. [RELEASED] Client mod loader Version 0.12 serverpacks Reference resources from other packs in mappings (bdew)
  9. [RELEASED] Client mod loader

    I left it out because the client beta branch already includes the modlauncher and there'd be a conflict if people would install both. However, for people not on the beta branch there's currently no "latest" modlauncher. I'll include it in the next version again.
  10. [RELEASED] Client mod loader Version 0.11 serverpacks Reload additional XMLs (budda)
  11. 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
  12. [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.
  13. 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.
  14. 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.
  15. I'm aware of the issue but did not have a chance to look into it yet.