1. Code:
    [Error] Error while compiling Meteors.cs(376,44): error CS0246: The type or namespace name `NetworkManager' could not be found. Are you missing an assembly reference?
     
  2. just replace in meteors.cs NetworkManager to HNetworkManager and save
     
  3. it works
     
  4. because it has stopped working after upgrading the server?
     
  5. meteor dont work after the new update 04-07-2016 to hurtworld. Who I fix this problem.
     
  6. Meteors | Page 4 | Oxide
     
  7. Smeag updated Meteors with a new update entry:

    1.0.2

     
  8. You need to add a ban on construction around the meteorite.
    [DOUBLEPOST=1469039213][/DOUBLEPOST]On my server after the fall of the meteorite players built its fence.
     
  9. Or.....you can make them drop in a no build area? There are 6 towns, the dome and carrier....that's 8 drop points right there.
     
  10. I have a lot of points of falling of a meteorite...
     
  11. Good news.
    I found a way to fix the delayed explosions. I already patched it and a update should come soon. It won't be perfect, but it was a massive improvement on my local server.
    Also, meteors will be able (under your choice) to destroy buildings. ;)
    Currently working on all the suggestions you guys gave me.
     
  12. Smeag updated Meteors with a new update entry:

    1.1.0

     
  13. You're awesome!
     
  14. I think you swapped the area and time in the language file....it says a meteor is set to fall at 5 in dome minute(s)....I just fixed the language file myself, but some may be confused by it. Actually when I edit it the language file it says a meteor is falling but never does.

    so 1 is time and 0 is the location? Here are some defaults in the language file:

    When the following happens it is correctly stated in chat
    "msg_meteorinfo_next": "<color=orange>Next meteor fall is in {0} minute(s).</color>",

    When the following happens it is correctly stated in chat
    "msg_meteor_located_fallwarning": "<color=red>A fiery meteor is falling near </color><color=orange>{0}!</color>",

    How can both be correct when the default for both is 0, and one of them for the time and the other is for the location?
     
    Last edited by a moderator: Jul 27, 2016
  15. Oh, I thought that I had fixed that. Taking a look now.
     
    Last edited by a moderator: Jul 27, 2016
  16. Smeag updated Meteors with a new update entry:

    1.1.1

     
  17. need to redo the lang file?
     
  18. @q1LLa
    Yes. Buy only 1 line has changed.
     
  19. Code:
    {msg_meteorinfo_current, "<color=orange>There is a hot meteor at </color><color=lime>{0}</color><color=orange>. It should be colder in </color><color=lightblue>{0} minute(s).</color>"}
    @Smeag you have not fixed the bug