Store Page
Starbound
All Discussions Screenshots Artwork Broadcasts Videos Workshop News Guides Reviews

Starbound

Store Page
Starbound >  Workshop > Oмεяυıп's Workshop > Hellish Planet: LEGACY > Discussions
Hellish Planet: LEGACY
Description Discussions2 Comments190 Change Notes
This topic has been locked
Oмεяυıп  [developer] 14 Mar, 2020 @ 11:57pm
♠♠♠Bugs/Issues♠♠♠
Encountered a problem? Let's figure it out!
You're gonna want to describe the problem to me, as well as grab your starbound.log from (Starbound>storage>starbound.log).

I only need the first, unnumbered starbound.log! Please open it and copy all the contents. If you would please, go to pastebin and post it there. Then you can grab the link to it and post it here!

With a description of the problem and the log, I'll do my best to solve the issue!
Last edited by Oмεяυıп; 19 Jul, 2021 @ 11:40am
< >
Showing 1-11 of 11 comments
Hektorsektor 9 Apr, 2020 @ 2:11pm 
https://pastebin.com/y7xj9z5K I cant beam to the planet...
#1
Oмεяυıп  [developer] 9 Apr, 2020 @ 2:46pm 
Originally posted by Hektorsektor:
https://pastebin.com/y7xj9z5K I cant beam to the planet...
Um, holy crap. Your game has a TON of errors, and none of them are caused by this mod in particular.
There's a ton of duplicate projectiles, missing assets, and apparently you must have a mod that changes the core biomes, because that is what is messed up, causing you to not be able to beam down.
I'd suggest looking over what mods you have, especially any that edit vanilla core biomes.
It also looks like "rubium" is bugging out the core biomes, so I'd check for mods that add scrapped vanilla (BETA) content.
#2
Hektorsektor 9 Apr, 2020 @ 2:56pm 
Thank You! :Smilingdemon:
#3
Hektorsektor 9 Apr, 2020 @ 3:15pm 
Okay I can beam down to the planet, but I still can't talk to npc-s, I have no dialogues. Have You ever got problems like that or know what could cause those?
#4
Oмεяυıп  [developer] 9 Apr, 2020 @ 7:21pm 
Originally posted by Hektorsektor:
Okay I can beam down to the planet, but I still can't talk to npc-s, I have no dialogues. Have You ever got problems like that or know what could cause those?
Wait, NPCs? There should be no NPCs on a Hellish planet... :demonsheep:
What do the NPCs look like? Are they vanilla or are they from a mod?
#5
Hektorsektor 10 Apr, 2020 @ 4:55am 
Both
#6
Oмεяυıп  [developer] 10 Apr, 2020 @ 10:29am 
Originally posted by Hektorsektor:
Both
Well that's really weird. I don't have anything within the mod that changes or adds NPCs to the planet, so I'm not sure. They should also still be able to talk whether they are on this planet or a different planet, too.
#7
Nullguy 17 Oct, 2020 @ 12:22pm 
It appears the new 'Vengeful Ghost' enemy you have added in update 1.4 causes the collections menu to throw an exception:

[14:55:47.968] [Error] Exception while invoking lua function 'selectCollection'. (LuaException) Error code 2, [string "/scripts/rect.lua"]:46: attempt to index a nil value (local 'rectangle') stack traceback: [C]: in metamethod '__index' [string "/scripts/rect.lua"]:46: in field 'size' [string "/interface/scripted/collections/collectionsgu..."]:54: in global 'populateList' [string "/interface/scripted/collections/collectionsgu..."]:85: in function <[string "/interface/scripted/collections/collectionsgu..."]:84> [0] 7ff6801da213 Star::captureStack [1] 7ff6801d8f9e Star::StarException::StarException [2] 7ff6801acfb1 Star::LuaEngine::handleError [3] 7ff6805c14ec Star::LuaEngine::callFunction<Star::String,Star::Json> [4] 7ff6805c1cbb Star::LuaFunction::invoke<Star::Variant<Star::Empty,bool,__int64,double,Star::LuaString,Star::LuaTable,Star::LuaFunction,Star::LuaThread,Star::LuaUserData>,Star::String,Star::Json> [5] 7ff6805c1bf1 Star::LuaBaseComponent::invoke<Star::Variant<Star::Empty,bool,__int64,double,Star::LuaString,Star::LuaTable,Star::LuaFunction,Star::LuaThread,Star::LuaUserData>,Star::String const & __ptr64,Star::Json const & __ptr64> [6] 7ff680a26b17 <lambda_1040602f3da4b220314d475ec2e86a01>::operator() [7] 7ff6809405f4 Star::ButtonGroup::wasChecked [8] 7ff680941d84 Star::ButtonWidget::setPressed [9] 7ff68094174a Star::ButtonWidget::sendEvent [10] 7ff6809711d7 Star::Widget::sendEvent [11] 7ff68095ec48 Star::Pane::sendEvent [12] 7ff680a2928b Star::ScriptPane::sendEvent [13] 7ff68096416d Star::PaneManager::sendInputEvent [14] 7ff6809eddb9 Star::MainInterface::handleInputEvent [15] 7ff680121e93 Star::ClientApplication::processInput [16] 7ff6808ed365 Star::SdlPlatform::run [17] 7ff6808ed68d Star::runMainApplication [18] 7ff680127731 WinMain [19] 7ff680ad07af __scrt_common_main_seh [20] 7ffbef447c24 BaseThreadInitThunk [21] 7ffbef74cea1 RtlUserThreadStart

Upon selecting the pets collection, the exception causes a blank space to appear as the last visible slot of the pet collections list. Anything that was supposed to appear beyond entry number 64 (I think that's supposed to be the pet's number on the list) will not be visible, and attempting to change the collection category doesn't do anything until the collections window is closed and reopened, provided that the collection that was last selected is not the pets collection.

I am assuming the issue comes from the 'Vengeful Ghost' for the following reasons:

1. Uninstalling this mod from my large set of mods fixes the issue, making it seem like the issue comes from this mod.

2. The issue only started happening after update 1.4, which added the 'Vengeful Ghost' without any other monsters added.

tl;dr: 'Vengeful Ghost' pet entry probably breaks pets collection menu, fixing it is probably a good idea yeah

Edit: Here is a pastebin of the session in case I missed something
https://pastebin.com/briHbT8b
Last edited by Nullguy; 17 Oct, 2020 @ 12:46pm
#8
Oмεяυıп  [developer] 17 Oct, 2020 @ 12:46pm 
Originally posted by Possibly exists:
It appears the new 'Vengeful Ghost' enemy you have added in update 1.4 causes the collections menu to throw an exception:

[14:55:47.968] [Error] Exception while invoking lua function 'selectCollection'. (LuaException) Error code 2, [string "/scripts/rect.lua"]:46: attempt to index a nil value (local 'rectangle') stack traceback: [C]: in metamethod '__index' [string "/scripts/rect.lua"]:46: in field 'size' [string "/interface/scripted/collections/collectionsgu..."]:54: in global 'populateList' [string "/interface/scripted/collections/collectionsgu..."]:85: in function <[string "/interface/scripted/collections/collectionsgu..."]:84> [0] 7ff6801da213 Star::captureStack [1] 7ff6801d8f9e Star::StarException::StarException [2] 7ff6801acfb1 Star::LuaEngine::handleError [3] 7ff6805c14ec Star::LuaEngine::callFunction<Star::String,Star::Json> [4] 7ff6805c1cbb Star::LuaFunction::invoke<Star::Variant<Star::Empty,bool,__int64,double,Star::LuaString,Star::LuaTable,Star::LuaFunction,Star::LuaThread,Star::LuaUserData>,Star::String,Star::Json> [5] 7ff6805c1bf1 Star::LuaBaseComponent::invoke<Star::Variant<Star::Empty,bool,__int64,double,Star::LuaString,Star::LuaTable,Star::LuaFunction,Star::LuaThread,Star::LuaUserData>,Star::String const & __ptr64,Star::Json const & __ptr64> [6] 7ff680a26b17 <lambda_1040602f3da4b220314d475ec2e86a01>::operator() [7] 7ff6809405f4 Star::ButtonGroup::wasChecked [8] 7ff680941d84 Star::ButtonWidget::setPressed [9] 7ff68094174a Star::ButtonWidget::sendEvent [10] 7ff6809711d7 Star::Widget::sendEvent [11] 7ff68095ec48 Star::Pane::sendEvent [12] 7ff680a2928b Star::ScriptPane::sendEvent [13] 7ff68096416d Star::PaneManager::sendInputEvent [14] 7ff6809eddb9 Star::MainInterface::handleInputEvent [15] 7ff680121e93 Star::ClientApplication::processInput [16] 7ff6808ed365 Star::SdlPlatform::run [17] 7ff6808ed68d Star::runMainApplication [18] 7ff680127731 WinMain [19] 7ff680ad07af __scrt_common_main_seh [20] 7ffbef447c24 BaseThreadInitThunk [21] 7ffbef74cea1 RtlUserThreadStart

Upon selecting the pets collection, the exception causes a blank space to appear as the last visible slot of the pet collections list. Anything that was supposed to appear beyond entry number 64 (I think that's supposed to be the pet's number on the list) will not be visible, and attempting to change the collection category doesn't do anything until the collections window is closed and reopened, provided that the collection that was last selected is not the pets collection.

I am assuming the issue comes from the 'Vengeful Ghost' for the following reasons:

1. Uninstalling this mod from my large set of mods fixes the issue, making it seem like the issue comes from this mod.

2. The issue only started happening after update 1.4, which added the 'Vengeful Ghost' without any other monsters added.

tl;dr: 'Vengeful Ghost' pet entry probably breaks pets collection menu, fixing it is probably a good idea yeah
Fixed!
Thanks. :cozybethesda:
#9
AquaMX 20 Jan, 2024 @ 2:10pm 
[UPD: Fixed it, the FU thing was the issue, if you want me to DEL this comment tell]

Having the same "can't beam / deploy down" issue as Hektorsektor, I'll give the pastebin and mod collection, I do play with a friend and they can't beam down either
Pastebin: https://pastebin.com/LUG6t6fM
Collection: https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=2994697062
Last edited by AquaMX; 21 Jan, 2024 @ 6:22am
#10
Oмεяυıп  [developer] 25 Jul, 2024 @ 6:41pm 
Originally posted by Aqua_The_Echidna:
[UPD: Fixed it, the FU thing was the issue, if you want me to DEL this comment tell]

Having the same "can't beam / deploy down" issue as Hektorsektor, I'll give the pastebin and mod collection, I do play with a friend and they can't beam down either
Pastebin: https://pastebin.com/LUG6t6fM
Collection: https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=2994697062
What specifically about FU was causing this particular problem?
#11
< >
Showing 1-11 of 11 comments
Per page: 1530 50