AlexRou

Registered Users
  • Content count

    789
  • Joined

  • Last visited

Everything posted by AlexRou

  1. The thread below is someone pasting a paragraph from wikipedia about a sand generating fish. Since his intent was to just put the information out there without knowing what to do with it, I thought I'd start a thread about an idea that came from it. The main idea is to have more interactions between creatures, plants and dupes. Even have them depend on one another for survival. Right now we have morbs that produce PO2, pufts that eat PO2 and poop slime and hatches that can eat slime and poop coal. However they can survive alone and isolated, would be interesting if they depended on each other for survival. What if hatches need O2 and pufts die without PO2 (can't remember if they do)? That would mean if you get rid of pufts then the morbs would produce a lot of PO2 and kill the hatches. If you get rid of the morbs then hatches would run out of PO2 and die. If you get rid of hatches, then the slime would just produce even more PO2 and you don't get coal. So with such a simple change we can make hatches depend on the survival of both morbs and pufts. Now imagine throwing plants and more creatures into the mix... This would give plants and creatures a much bigger role and importance than just sources of food/coal/slime.
  2. dude ... ew ... thanks for that image
  3. Well there are 2 routes we could take this, a parasite or a symbiote. A parasite would yes have no good sides and would be similar to a disease. A symbiote would be something that needs a dupe and the dupe would need the symbiote and in return the symbiote has some benefits for the bad sides. I think the symbiote route would be super interesting as the pros would be very tempting but the cons could get deadly. So players would have to very carefully decide and manage such dupes. Also I don't think anyone would want to voluntarily equip a parasite lol so for it to make sense to be equipable it would have to be a symbiote.
  4. The bad sides could be stuff like Not being able to unequip it without gaining a ton of stress and the dupe dies within a cycle or something Or not being able to unequip at all Dupe dies after X cycles counting from the first equip Normal dupes shun you But in return you can get stuff like increased heat resistance, stats, etc... Maybe for lulz add a small chance the parasite takes over and starts converting everyone. Or maybe make it a 100% chance thing after X cycles, so you have to kill the dupe before it matures. Dude we were both talking in that thread lol. Thats interesting .... this fits quite nicely actually. Maybe let dupes carry it up/down ladders so they're a little easier to handle.
  5. Sorry I used creature as in something instead of creature as in animals lol. But hey alien creatures could breathe CO2 for all you know btw you got any ideas for creatures/plants with a symbiotic relationship with dupes? Was trying to think of one but nth really comes up except ... you know ... infected dupes that wants to take over. Maybe not exactly symbiotic, just some creature/plant that cannot live without dupes.
  6. I guess that makes sense, knowing these kinds of things before building would indeed help.
  7. That sounds like an interesting paper to read if someone wants to figure out why
  8. Was just giving an example to show the idea without thinking too much into it. But yeah the spawning and living conditions would need to be changed. If no creature in the ecosystem produces CO2 then I don't think it would be a problem, if you dug out a area and dump in CO2 then yes that should be a problem a player needs to deal with. Like how we are ruining ecosystems today, we ruin the perfect environment of the creatures. If a creature produces CO2 then there should be one to consume it.
  9. Can you give an example? Screenshot would be nice.
  10. I understand your idea is to get sand. What I don't understand is do you want a single creature that produces sand or are you asking for a underwater biome which includes the parrot fish + shark + sponge + coral + everything else.
  11. In the invite message I got they said So yeah best way is to post a lot, not spam, really discuss ideas in detail and hope they notice you if and when they decide to add more people. You can start by picking a random thread and debating the ideas in it. Do not simply say "me too", give intellectual comments whether you think it would work or not. Maybe even add on your own ideas while explaining how and why it would add to the original idea. What any dev needs are people that can debate ideas so they have a clearer picture of the idea instead of everything being one sided. Which is the whole point of closed testing, you want feedback from a small group of people but you don't want everyone of them saying "I like it", you want them to point out bad things and explain why they are bad and how they can do better. They don't need people who just play the game and report if something is broken.
  12. I'll save you guys time by saying the devs have said countless times that there will not be multiplayer in any form for ONI as it would take the same amount of effort as creating a whole new game.
  13. 2.14 works fine, looks like it's your drivers.
  14. I was giving a number that would work most of the time without having to decide on materials or worry about how much water is in it. With the pressure display it would not indicate to you which cycle it would break. As for will it break and where ... I don't think it is a important enough question to have a dedicated pressure display. Which is why I said to just make it 3 tiles thick, if 3 layers of tiles is good enough for most situations then what would be the point in knowing if a block will break? There is no better shape than a box, pressure is based on the block of water directly touching the tile so any other shape would have no meaning.
  15. Black screen of death

    Completely black? As in absolutely nothing on the screen? Attach this file: SteamApps\common\OxygenNotIncluded\OxygenNotIncluded_Data\output_log.txt
  16. You can easily get around the 1kg loop by mopping the floors.
  17. Nope, the easiest explanation is that the map is just a slice of the whole asteroid. Even with extreme centrifugal/tidal forces, having actual magma is highly unlikely, it would prob just break itself apart before forming magma.
  18. Can you please explain your idea instead of copy pasting wikipedia.
  19. Transistor

    Just remembered ... we're missing a tone generator too.
  20. The game crashed!

    You need a graphics card to play the game. I am not sure if your machine is capable of a upgrade so you might need an entirely new PC.
  21. You can't do anything more clever than a box sadly. Just make it 3 tiles thick and it should be fine most of the time. I'm not too sure of any usefulness of such a display.
  22. Most of those we won't be able to answer since it would have to be implemented to find out. If it only allows micro tasks directly in the path then increase in pathfinding time should be negligible since we can do the check at the final stage of A* where it constructs the path and since we are iterating over the nodes anyway the increase would be the time it takes to check the list on each node. They could even just check when a dupe is in a new square if there is a micro task in it. If the queue system is what I expect it to be then it shouldn't be too long a dev time, prob longer for testing and fine tuning of the numbers. This is the most important question and the only one we can definitely answer, but I think we need more people giving their opinions. For me I think it makes sense for things that take up almost no time at all. But maybe they could ignore it for priority 9 so we have a emergency priority where even stopping for half a second is too long.
  23. If they had a separate list for micro tasks (tasks that take up no more time than simply walking there, like switches) while also queueing up the micro tasks in the global queue, then when assigning a task to a dupe during the pathfinding stage they could do a check to see if it will pass by a unassigned micro task and tell the dupe to do that first and then it's original task.
  24. Transistor

    Someone is soo gona make a CPU with those
  25. Transistor

    But no one is going to understand what it does from the name Retardator. Someone would think it turns dupes into retards. And from your descriptions people would think you are talking about controlling time.