Version Found - [W|0.0.25B]
Title - Fire was not responded to, and could not be prioritized. Destroyed part of colony.
Summary - An electrical explosion caused a massive inferno in one of my rooms. After the colonists diligently fought this fire, everything inside had been destroyed (six equipment racks.) However, before the fire was out, it had spread (through a 1-square thick rock wall) to the adjacent rooms, burning a potted plant and a research table. After taking care of the first fire, the colonists moved to fight the potted plant fire. But, once it was out, not a single colonist moved for the research table fire; in fact, they all went to bed. I attempted prioritizing it with all of them, but the only message that would come up would be "Cannot prioritize (Colonist is not a researcher)." After allowing all colonists to research, I again tried prioritising the fire, getting instead the message "Cannot prioritize (Research is a long-term task.) I thought to disallowing all tasks other than research and trying again, but by this time the table had burned down. I suspect the problem here is that the firefighting range is only 1 block; they could not deal with the threat because the fire was on the wall side of the table. Please fix; set firefighting range to 2 blocks or come up with another solution.
Steps to Reproduce -
1. Fire breaks out.
2. Fire spreads through 1 block thick rock walls into two adjacent rooms; one has a burning potted plant, the other has a burning research table facing the wall.
3. Colonists fight first fire.
4. Colonists fight fire in second room.
5. Colonists fail to fight fire on the back of the research table.
6. Research table is lost.
Expected Results - Expected colonists to fight the fire.
Actual Results - Colonists let the table burn down.
did you set your home zone?
If you havent set the homezone they wont start putting out fires
If they have priorities higher than firefighting they wont aswell (-;
please check these things and let us know.
Forgot to mention. Home zone was indeed set in that area. (verified, loaded a save from seconds before the explosion) I keep my home zones up to date. When the fire spread from the block in the back of the table, colonists responded, but they still wouldn't fight the fire in the back. This is the diagram of the room; the X is where the fire was not fought. The L is a standing lamp.
I'll draw a diagram.
[][][][][] [][][][][] [][][][][] [][][][][] []
[]R R L P[]E L E E L E[]R R P L P[]
[]R R []E C C E[]R R C C[]
[]R R []E C C E[]R R C[]
[]R R []E C C E[]R R C[]
[]R R []E C C E[]R R C C[]
[]L L[]E C C C C E[]L C C C L[]
[][][]--[][][][][][]--[][][][][][]--[][][][]
Key:
[] = Rock
R = Research Bench
L = Standing Lamp
P = Potted Plant
E = Equipment Rack
C = Conduit
-- = Door
Disregard spaces in walls, that was to compensate for [] =/= --
Strikethrough = Burning
Underline = Not fought
The lower left corner of the Research Bench fire was not fought. Whenever it spread, colonists would fight what it spread to, but not the back of the research bench.
Can you upload the save so i can confirm this.
Than i will upload this to mantis with the save.
Thanks alot.
I'm not quite sure how to do that, but I'll give it a try.
It was an autosave and I've been playing since -_-. Closest save I have is seconds after it happened. Either that, or two days before, and I'm not sure the same thing will happen. I can upload them both to verify that the home zone was indeed activated, but other than that, I can't help anymore.
Colonists can only fight fires in squares they can stand adjacent to. So if a fire gets started in a square they don't have adjacent access to, such as the middle of a paste dispenser or a solar panel array, there's nothing you can do. My recommendation for those events is to draft every nearby colonist and have them shoot the burning building - no fuel, no fire.
The real bug here is that fire spread through a one-tile rock wall. What, was it giving off quantum-tunneling embers?
Exactly my point; the thing spread somewhere it really shouldn't have, without even touching the rooms it would have to go through to get there. I can sort of understand it if the rocks were extremely heated, but even then, it would take a good amount of time for the heat to build up enough on the other side for a fire to break out.
If sparks are passing through rocks, that may be a bug.
Just happened to me again. I un-home zoned the initial room to see it the fire would spread through the rock again. Indeed it did. I saved right after the fire broke out. I uploaded the save below... is what I would say if I knew how to access save files.
ALSO, this is [W|0.0.254] NOT 254b. I assumed that since I got the game two days ago that it would be the b version, but it isn't. This bug may still be relevant though.
Save files are in /user/appdata/localflow/ludeon/rimworld
remember to make sure your browser shows hidden files and folders.
Still unable to find them. I've set my search to include all otherwise hidden results, including my operating system files, and I still can't find it. I even looked at every file/folder in appdata and in the search that came up for app. I looked in every folder containing the word RimWorld, and there are no folders containing the word Ludeon.
I don't have my RimWorld data in the standard spot, but it's in the same place I downloaded it to, if that helps. What should I search for? What is the file extension I'm looking for? Does the save file have the same name as it does in-game? (searched for it and didn't find it.)
It is not about where you have your rimworld stored it always makes a folder in
C:\Users\%user%\AppData\LocalLow\Ludeon Studios\rimworld\ [savegames]
The extra Studios part may be what screwed me over. I'll check in an hour when I have access to my computer again. (Sent from mobile.)
Finally found the damned thing. I guess my problem was using the Start Search instead of peeking through folders on my own. here it is. Remove the home zone where the fire is and watch it spread through the rock walls (possibly may not happen every time, but do a few repetitions for good measure.)
Had to compress it for it to go. Hope that doesn't skew the results.
[attachment deleted by admin: too old]
... So what, is nobody going to actually validate this now?
Quote from: JKTD1919 on December 04, 2013, 09:40:55 PM
... So what, is nobody going to actually validate this now?
Sorry jktd1919 i completely forgot this one my bad...
I will check it now.
Thanks Semmy. :)
First off you are running version .254 instead of .254B (see screenshot.)
Make sure you get the latest version. Don't run you'r old savegames they wont work well in newer versions.
And thanks for reporting the bug.
[attachment deleted by admin: too old]
I did and it is registered...
I already put it in yesterday.
Thats why i said thanks for reporting the bug.
... I'm sorry, I feel like a real dick now. I ought not act like that. Sorry, Semmy. I misunderstood.
No problem at all.
Enjoy the game.
That dialog you see is actually a bug.
It appears when the versions are different, as they are in this case.
However, they're only different by a couple of numbers in "rev". What is rev? It's number of seconds since that day started divided by two. Which means these were two different builds created within a few seconds of each other. Which means what actually happened was that you saved the game on the build for one OS, and loaded it on another that gets built later in the build process and thus has a slightly different number.
They're both 254b.
Thank you very much for clearing that up, Ty.
We already added this bug to the bugtracker btw (-:
thanks again for helping out and once more sorry i forgot to finish my job
Thank you, Semmy. You pull a lot of weight around here, so I don't blame you.