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
(Note: I love these things. Thank you Devs).
Summation: Archotech ship airlocks can become immortal to all damage if used with airlock beams.
Methodology: Tester replicated event 250 times 3 times using in game construction and 247 times using dev mode.
Description (general): The new airlock beams are great; they permit breathable air links between ships with toggle docking. One beam is placed on either side of the airlock (door). They extend to form a “bridge” between air locks. Useful for docking smaller or larger ships.
Original Presentation: Using airlock beam as intended to dock two ships. Docked ship and extended airlock bridge were destroyed in combat. Archotech door remained at 0/1000 HP. Testing resulted….
Description (Event): Tester placed an airlock beam on either side of a standard ship airlock. No problems. However, airlock beams on either side of an archotech ship airlock results in an archotech airlock that cannot be damaged, or destroyed. Dev commands of “destroy,” “kill” “clear area (rect) do nothing. Dev mode explosions of bomb, and other events are powerless against the immortal Archotech ship airlock, which simply shall not die.
“Bug to Feature Solution:” Tester created a line of these immortal archotech ship airlocks. They block incoming enemy fire (railguns, plasma, lasers, and uranium slugs, torpedoes). Gaps exist between immortal archotech airlock doors, but repeated lines were hypothesized to serve as intercepting armor against enemy attacks. This generated the dev desired error logs.
Image: #1.4exp: 1.1
https://imgur.com/a/HmwOzS3
Explanation: Archotech ship airlock is at 0/1000 HP.
Area A shows these airlocks block enemy fire including dev spawned bomb explosions.
Area B are the airlocks themselves.
Dev Error Log $1.4exp: 1.1
Explosion could not affect cell (266, 0, 272): System.NullReferenceException: Object reference not set to an instance of an object
at RimWorld.Building_ShipAirlock.UnDock () [0x000d1] in <468f2d18d6424a7ea55cd7be85d45af4>:0
at RimWorld.Building_ShipAirlock.Destroy (Verse.DestroyMode mode) [0x0000c] in <468f2d18d6424a7ea55cd7be85d45af4>:0
at Verse.Thing.Kill (System.Nullable`1[T] dinfo, Verse.Hediff exactCulprit) [0x00000] in <3126aca1aad041dcbdeda807cfe004bf>:0
at Verse.DamageWorker.Apply (Verse.DamageInfo dinfo, Verse.Thing victim) [0x00172] in <3126aca1aad041dcbdeda807cfe004bf>:0
at (wrapper dynamic-method) Verse.DamageWorker_AddInjury.Verse.DamageWorker_AddInjury.Apply_Patch2(Verse.DamageWorker_AddInjury,Verse.DamageInfo,Verse.Thing)
at (wrapper dynamic-method) Verse.Thing.Verse.Thing.TakeDamage_Patch2(Verse.Thing,Verse.DamageInfo)
at Verse.DamageWorker.ExplosionDamageThing (Verse.Explosion explosion, Verse.Thing t, System.Collections.Generic.List`1[T] damagedThings, System.Collections.Generic.List`1[T] ignoredThings, Verse.IntVec3 cell) [0x00127] in <3126aca1aad041dcbdeda807cfe004bf>:0
at Verse.DamageWorker.ExplosionAffectCell (Verse.Explosion explosion, Verse.IntVec3 c, System.Collections.Generic.List`1[T] damagedThings, System.Collections.Generic.List`1[T] ignoredThings, System.Boolean canThrowMotes) [0x00212] in <3126aca1aad041dcbdeda807cfe004bf>:0
at Verse.Explosion.AffectCell (Verse.IntVec3 c) [0x0007d] in <3126aca1aad041dcbdeda807cfe004bf>:0
at Verse.Explosion.Tick () [0x0003d] in <3126aca1aad041dcbdeda807cfe004bf>:0
UnityEngine.StackTraceUtility:ExtractStackTrace ()
Verse.Log:Error (string)
Verse.Explosion:Tick ()
Verse.TickList:Tick ()
(wrapper dynamic-method) Verse.TickManager:Verse.TickManager.DoSingleTick_Patch2 (Verse.TickManager)
Verse.TickManager:TickManagerUpdate ()
(wrapper dynamic-method) Verse.Game:Verse.Game.UpdatePlay_Patch2 (Verse.Game)
Verse.Root_Play:Update ()
Even posting in discussion section where people regularly bring up bugs. The discussion page is all bug reports, many of which I have helped troubleshoot. These include matters with "building ship tiles," "a manifold related to the J/T drive" and a white screen after an attempt at lauching a ship.
Please reevluate your chosen behavior. Thank you. Feel free to throw exclamation points at someone who is not me. Or perhaps better yet, not at anyone.
On second thought, perhaps I just won't use this, troubleshoot it, and/or test it anymore. This is not a choice that will be left to individuals who behave like this.
Thank you for the opportunity to assist in your emotional growth. I understand you may be upset about something that likely does not involve me and are redirecting. I don't take it personally. I suggest you consider the manner in which you chose to deal with people who are assisting you in the future. Thank you.
Raging at people trying to assist with something simply does not work.
I might decide to post one more, unsure. You're welcome.
Steam is basically Valve's storefront. They don't want to create a community where developers and users can interface. They just want your wallet, and opinions, which drive pageviews. Where workshop is concerned, that makes it even more inconvenient.
Thanks
Your self imposed assumptions are not mine. Your approach = very flawed.
I knew you were not SoS Dev, and I was unwilling to tolerate your rudeness.
I am "chill," with calm speech. Notice who (still) uses multiple exclamation points....
Your being self = coder and self = upset does not justify your behavior.
Every action has an equal and opposite reaction. Learn from Thain's example.
Thain's approach and yours are polar opposite. Hence polar opposite reaction.
Again, "Raging at people trying to assist with something simply does not work."
I recommend you take this truth into account and alter behavior accordingly.
I again invite you to examine your behavior. Else, you risk repeating your mistake.
Thank you. Have a good night.
You can expect people to react when you scream at them and order them around when they are attempting to assist, in ways you do not desire. You behaved in a manner they did not desire, they returned it. Such is the world.
It did not matter if you were SoS dev or not and your assumption that it did was flawed. I decided that *anyone* yelling at me for donating my time to do detailed product testing on video game structural features, rather than having fun with said video game was not worth it.. The price you imposed of being yelled at is not worth the time investment of providing the testing. It also does not paint an inviting picture of participating in this community if that's how it is going to be.
You are being approached as a rational adult. The fact that you are uncomfortable with the situation created by your screaming does not mean it is not "chill" on my end The fact that I am not agreeing with your assessment of the situation does not meat it is not "chill."
Again, when you scream at and order people around with no reason, because you are upset, some of us will call you on it. That's called life. This is a very polite version of that.
I have no indication that you intend to learn from your bad behavior of screaming at and ordering people around. That is unfortunately for you. Thus, if you would like to continue a civilized conversation, that might occur. if you chose to keep screaming at people, ordering them around, and then demanding they see the world your way with no explanation after you have behaved this way, then I see no point in this. You may continue this conversation without me if you carry on this way.
Ultimately and as I stated, you can learn form Thain's example, or just continue posting as you have: screaming, ordering people around, and insisting you are right based off unproven assumptions while scaring away product testers.
Choice is yours. Chose wisely, have a good night. I'm out.
Edit: you appear to have edited your post while I was posting. No I was not told by the dev to do any such thing. I would recommend you drop this fruitless conversation, but realize you may continue it without me.
@Thain sorry if this nonsense has been pinging your notifications, im quite done now. hope you have a nice night.
Don't feel like doing anymore testing logs. Good bye.