Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=2819371233
Hope it helps anyone!
just left it on full speed,
(time it took of my pawns to stave to death :P,,, nothing happened to the mechnoids (vanillah ones)
blasting them with the dev modes flame explosion, and 10000 flame damage effects them, but having them roost to dea.... malfunction doesn't seem to do anything to the mechs nore they're equipment :S:S:S
just see the "comfortable temperature range - 100c - 250c on the gear tab for the centi,
(and its heavy charge blasters at (normal) , its health tabs not shown any "injuries" yet
just booked a "sickie" off work :P....
just spawned a (mech_centipede, lancer and scyther into that test room)
ill hit ya up if theres any issues,
as for the raiderpedes.
fair point :). i know we're asking a lot with the raider-class creatures, so i for one,, dont fancy putting more work onto your plate if ya revive the mods :)
sorry about having to dash... ill check back in once i finish
(facepalms)
spawned 3 of the centipedes and walled off a raiderpede so it wouldn't get attacked...
set up th sweat box with 80 heaters,,,,,,,,,,,
but like a noob..... i took a screenshot and exited the game instead of testing it out first lol...
(sadly now i cant re-build the box as i gotta dash now :S .... ill get the screenshot uploaded so you get a rough idea of what i did to try test it
mod-e
core
mod manager
raiderpedes
mechnoids feel chill
before i gotta dust for work ... >.<
(i figure,,, maybe ? "just maybe" the a dog said as done something to how they act (shrugs)
are
mod-e
"core"
mod manager
prepare carefully
detailed body textures
hugslib
no debris
a dog said...
muffalant
muffalant : a dog said
raiderpedes
mechanoids feel chill now
i've just built a "sweat box" to test this out while im getting the mods im after using.
i've built 80 heaters all clocked up at 1101c, fully powered, in one section,
a wall full of vents inbetween the heaters and the sweatbox,
fully roofed with steel walls 2 squares thick encasing the sweat box with deep water to prevent the mechs getting out.
spawned living creatures in there as well as a control creature.
-----------------------------------------------------------------------------------
the living creatures got massive heatstroke almost instantly,
altho i've had it running on the fastest speed for 5 mins, while watching the mech's health tab,
but sadly they havn't shown up heat-stroke or limb damage or even died or exploded (in their case)
https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=846222458
The game seems to play ok with the error... I suspect this Mech doesn't have the vulnerability that your mod provides. - I love to fry them in a room of fire. :)
Thanks.
I am playing a new game (previous one no problems) with a few more mods and am getting this error at game startup after maybe 20 hours playtime.
(Red) Config error in MechanicalAssaulter: no parts vulnerable to frostbite
Verse.Log:Error(String, Boolean)
Verse.DefDatabase`1:ErrorCheckAllDefs()
System.Reflection.MonoMethod:InternalInvoke(Object, Object[], Exception&)
System.Reflection.MonoMethod:Invoke(Object, BindingFlags, Binder, Object[], CultureInfo)
System.Reflection.MethodBase:Invoke(Object, Object[])
Verse.GenGeneric:InvokeStaticMethodOnGenericType(Type, Type, String)
Verse.PlayDataLoader:DoPlayLoad()
Verse.PlayDataLoader:LoadAllPlayData(Boolean)
Verse.Root:<Start>m__1()
Verse.LongEventHandler:RunEventFromAnotherThread(Action)
Verse.LongEventHandler:<UpdateCurrentAsynchronousEvent>m__1()
Any thoughts?
When I disable the mod, the error(s) go away. Thanks for any help you can provide.