1. Please be advised of a few specific rules and guidelines for this section.

RELEASED Natural Slopes (replacer version) 1.3.9.25

Replaces default block rendering with a custom slope render.

  1. Custos_Aeternam

    Custos_Aeternam Void-Bound Voyager

    Custos_Aeternam submitted a new mod:

    Natural Slopes (replacer version) - Replaces default block rendering with a custom slope render.

    Read more about this mod...
     
  2. Mooncalf99

    Mooncalf99 Spaceman Spiff

    I've run into a... problematic bug with your mod. Sometimes when excavating a fossil, the window is broken. Not the older "glitchy but technically workable" one, but rather this:
    fossil interface bug.PNG
    I.e. literally nothing to work with. The log gets this error message: https://pastebin.com/rE3LQjRN

    The error seems to be biome-tied, or possibly tied to the surrounding blocks. In some areas, such as the Sulphuric biome I was in at the captured event, it comes up for every fossil I try with. In other areas, it seems to be more sporadic. In one place, I noticed that if I put timber blocks to stand on and surround the fossil with (I like to keep monsters out when I'm working), the bug triggered, whereas if I used natural blocks it was fine.

    And yes, I know this mod is the cause, as I tested on the exact same fossil (by backing up and restoring world files) with and without the mod, and the excavation worked fine without it.

    I hope this provides some clues as to what's wrong so you can fix it. The world is so much more aesthetically pleasing with slopes.
     
  3. Custos_Aeternam

    Custos_Aeternam Void-Bound Voyager

    Sorry, forgot to update this one with the steam version; I fixed that issue.
     
  4. Custos_Aeternam

    Custos_Aeternam Void-Bound Voyager

    Also, when you run into "Glitchy but workable" fossils, please copy and paste your log to pastebin.com and put it here so I can correct it. I have the script logging when a file is not supported.
     
  5. Custos_Aeternam

    Custos_Aeternam Void-Bound Voyager

  6. Custos_Aeternam

    Custos_Aeternam Void-Bound Voyager

  7. Custos_Aeternam

    Custos_Aeternam Void-Bound Voyager

  8. Custos_Aeternam

    Custos_Aeternam Void-Bound Voyager

    I might, perhaps, maybe, also upload the "crafting" version so that people who, for some reason, don't want slopes to generate naturally can craft them.
     
  9. Custos_Aeternam

    Custos_Aeternam Void-Bound Voyager

    I am heavily debating on reworking this mod from its original state into one that will be significantly easier to update.
    Right now I am adding each file I want the fossil game to load and editing the level.lua to swap the file it is using for the one I want it to use... which means every image the fossil game uses exists in two separate forms.
    If I were to move the sloped textures to a different folder, and edit the materials.patch files to point to the images' new location it would preserve the vanilla images and allow the fossil game to load any texture it wants.
     
  10. Mooncalf99

    Mooncalf99 Spaceman Spiff

    Got kicked back to ship while exploring the lower depths of a planet. When I checked the log, I found this:


    [21:01:42.513] [Error] |----------That Dirt material : /tiles/materials/fmud.png is not supported yet!

    I left the textures wonky so that you would report it! :D
    [21:01:42.513] [Error] |----------That Rock material : /tiles/materials/fcobblestone.png is not supported yet!

    I left the textures wonky so that you would report it! :D
    [21:04:24.494] [Info] Root: Writing runtime configuration to '..\storage\starbound.config'
    [21:04:34.510] [Info] Root: Writing runtime configuration to '..\storage\starbound.config'
    [21:07:24.724] [Info] Root: Writing runtime configuration to '..\storage\starbound.config'
    [21:07:33.570] [Error] WorldServerThread exception caught: (WorldStorageException) WorldStorage generation failed while generating from queue
    [0] 7ff66ac8a213 Star::captureStack
    [1] 7ff66ac88f9e Star::StarException::StarException
    [2] 7ff66ac89088 Star::StarException::StarException
    [3] 7ff66b22d4b0 Star::WorldStorageException::WorldStorageException
    [4] 7ff66b627568 `Star::WorldStorage::generateQueue'::`1'::catch$156
    [5] 7ff8ce401030
    [6] 7ff8ce403298 is_exception_typeof
    [7] 7ff8fabd3cc6 RtlCaptureContext
    [8] 7ff66b230aed Star::WorldStorage::generateQueue
    [9] 7ff66b224788 Star::WorldServer::update
    [10] 7ff66b22a0a6 Star::WorldServerThread::update
    [11] 7ff66b229a8b Star::WorldServerThread::run
    [12] 7ff66ac86d9e Star::ThreadImpl::runThread
    [13] 7ff8fa2a7974 BaseThreadInitThunk
    [14] 7ff8fab9a271 RtlUserThreadStart
    Caused by: (TreasureException) Unknown treasure pool 'scienceoutpostbanner2'
    [0] 7ff66ac8a213 Star::captureStack
    [1] 7ff66ac88f9e Star::StarException::StarException
    [2] 7ff66b10dede Star::TreasureDatabase::createTreasure
    [3] 7ff66b10e62d Star::TreasureDatabase::createTreasure
    [4] 7ff66b10e62d Star::TreasureDatabase::createTreasure
    [5] 7ff66b10e62d Star::TreasureDatabase::createTreasure
    [6] 7ff66b10ebc4 Star::TreasureDatabase::createTreasure
    [7] 7ff66b10f2a6 Star::TreasureDatabase::fillWithTreasure
    [8] 7ff66b29239a Star::ContainerObject::init
    [9] 7ff66b20901e Star::WorldServer::addEntity
    [10] 7ff66b1c2297 Star::WorldGenerator::prepareSector
    [11] 7ff66b1be064 Star::WorldGenerator::generateSectorLevel
    [12] 7ff66b230e20 Star::WorldStorage::generateSectorToLevel
    [13] 7ff66b230aed Star::WorldStorage::generateQueue
    [14] 7ff66b224788 Star::WorldServer::update
    [15] 7ff66b22a0a6 Star::WorldServerThread::update
    [16] 7ff66b229a8b Star::WorldServerThread::run
    [17] 7ff66ac86d9e Star::ThreadImpl::runThread
    [18] 7ff8fa2a7974 BaseThreadInitThunk
    [19] 7ff8fab9a271 RtlUserThreadStart
    [21:07:33.610] [Error] UniverseServer: World CelestialWorld:115538257:5765882:40208561:5 has stopped due to an error
    [21:07:33.610] [Info] UniverseServer: World CelestialWorld:115538257:5765882:40208561:5 shutdown, kicking 1 players to their own ships
    [21:07:33.713] [Info] UniverseServer: Loading client ship world ClientShipWorld:f6e8dc5ebbfa89c4452ccd87ecb37dc0
    [21:07:33.814] [Info] Protected dungeonIds for world set to (65524)
    [21:07:35.388] [Info] UniverseServer: Warping player 1 to ClientShipWorld:f6e8dc5ebbfa89c4452ccd87ecb37dc0
    [21:07:35.450] [Info] Client received world stop packet, leaving: Removed

    Well, I've reported it now. Please fix so it doesn't break things again.

    Also, if you're going to put in forced errors for testing, consider having your error message say which mod is doing it. I run a lot of them, and it took some digging to find the culprit.
     
  11. Custos_Aeternam

    Custos_Aeternam Void-Bound Voyager


    I love how you assumed immediately that my mod had anything to do with your crash.
    " [Error] WorldServerThread exception caught: (WorldStorageException) WorldStorage generation failed while generating from queue
    -snip-
    Caused by: (TreasureException) Unknown treasure pool 'scienceoutpostbanner2'
    -snip-"
    ^ ^ ^ ^ ^That caused it.
    My script broke because something else messed with lua. There is no way for my script to tell which mod broke, all it is doing is testing to see if x texture is supported. In this case, something caused the LUA to act weird and think that the very valid textures that I put in the mod are not valid.
    Surprise surprise, your error was actually cause by something else. Which I quoted above. That error is the reason you were kicked to your ship and has nothing to do with my mod. There is nothing I can do to fix that.
    All my script does is intercept the textures being given to the fossil game, check if they are one of the supported textures, and, if they are, it gives the fossil game the names of the proper textures (which have f added to the front of them).
    The rest of the mod also doesn't cause the problem you posted.
    The funny thing about this error, is that it should still have given the fossil game the correct textures, since it somehow got ahold of the f-names sooner than it should have.
     
    Last edited: Nov 29, 2019

Share This Page