Content: Slate Blackcurrant Watermelon Strawberry Orange Banana Apple Emerald Chocolate Marble
Background: Slate Blackcurrant Watermelon Strawberry Orange Banana Apple Emerald Chocolate Marble
Pattern: Blank Waves Notes Sharp Wood Rockface Leather Honey Vertical Triangles
Welcome to TerraFirmaCraft Forums

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.

  • Announcements

    • Dries007

      ATTENTION Forum Database Breach   03/04/2019

      There has been a breach of our database. Please make sure you change your password (use a password manager, like Lastpass).
      If you used this password anywhere else, change that too! The passwords themselves are stored hashed, but may old accounts still had old, insecure (by today's standards) hashes from back when they where created. This means they can be "cracked" more easily. Other leaked information includes: email, IP, account name.
      I'm trying my best to find out more and keep everyone up to date. Discord (http://invite.gg/TerraFirmaCraft) is the best option for up to date news and questions. I'm sorry for this, but the damage has been done. All I can do is try to make sure it doesn't happen again.
    • Claycorp

      This forum is now READ ONLY!   01/20/2020

      As of this post and forever into the future this forum has been put into READ ONLY MODE. There will be no new posts! A replacement is coming SoonTM . If you wish to stay up-to-date on whats going on or post your content. Please use the Discord or Sub-Reddit until the new forums are running.

      Any questions or comments can be directed to Claycorp on either platform.

Darmo

Contributor
  • Content count

    828
  • Joined

  • Last visited

Everything posted by Darmo

  1. Since we have been getting a lot of interest in MCMC, I thought it would be best if I made a rough tutorial. I tried to write this for a total beginner, but it's also good for people familiar with Techne, but new to MCMC, to catch some of the less obvious tricks and functions. The tutorial is divided into two parts: Mechanics, which is a button-by-button explanation, and Key Concepts, which covers some of the key ideas and methods to making a good working model in MCMC. If you are thinking of applying to make models for TFC2, please also read the TFC2 Model Guidelines post, and contact Darmo. I apologize for the spoiler issues. I can't figure out how to delete a spoiler once created (irony) MCMC MECHANICS Basic instruction for anyone wanting to use MCMC. Here I will try to explain things that are not dead-obvious. KEY CONCEPTS OF MCMC Z-FIGHTING ELEVATION It's ok to have your mob elevated above the turf block when working on it, but in the final version for insertion into the game, the mob must have it's feet on the turf block (Or if it doesn't have legs, it must otherwise be in the relation to the turf block that it needs to be in game) TRANSPARENCY TIPS & TRICKS This sections is for suggestions and tips that some of us contributors think might be helpful to those attempting to model with MCMC whether for TFC2 or not. They may or may not be useful for you START WITH THE HEAD UNDERSTAND TEXTURES
  2. Texturing Tutorial

    I thought it might be helpful for budding modelers to have an idea of how to approach textures. I'm far from a great texturer, but I think I get decent results, and this is the process I use. I'm not going to go into the technicalities of actual commands in the image editors - you're on your own there, and you might need to read some other tutorials to learn the image editing program. First you’ll need an image editor. If you don’t have one, gimp is a good free one. After you have an editing program, export your model’s texture map. You will now have a .png file with colored shapes. Hopefully you already understand how these shapes relate to the boxes in the model. If not, you should play around with the shapes, put some numbers on them or something, so that you know which shape is which. Save/export it to PNG, load the image into your model's texture map, and see how things show up. Once you have a grasp on how the shapes relate to the boxes, you're ready to work on your texture. Export a fresh texture map if you have to. This will be your base file. Open it. Make a separate layer, and call it background. Name the layer with the texture map something like ‘texmap’ or whatever. Make this texmap layer translucent, and keep it above all other layers. This way you can turn it on for reference, but still see through it, and work under it on a separate layer. Next find an image of the animal on the internet. One that has the colors you want to use, in good lighting. I find this to be easier than trying to pick from a color wheel. Find an area of the animal’s hide that has even lighting, and is relatively free of shadows and folds. Copy an area of the animal’s hide that is approximately the size of your texture. Paste it into your image editor (you may want to use a separate one, such as paint.net). Use the blur filter to further blur out fine details such as hair, which will probably be too jarring for your texture, which will be far smaller than the photo. It should be fairly smooth, with very subtle gradation. Now do a noise filter. The noise filter adds small artifacts in a random and evenly distributed fashion. This gives texture to the image, without being overwhelming. I often apply these filters separately, in paint.net, another image editor, so as not to mess with the layers I already have in gimp (I'm not super-skilled with gimp to know how to keep this from happening).Play with these filters until You like what you see. Now copy and paste it into the background layer in gimp. Use the clone stamp tool to get rid of any areas of shade or detail that stand out too much. This becomes the base color of your animal, and will cover the entire field. Put this on it’s own layer, and do not change it. This is now the default background for the entire animal. This layer will always be on the very bottom, and the texmap on the very top. Do not change either of them. By having one large base texture, you avoid a lot of copy-paste detail work trying to fit a base texture to every square of every box. With a nice generic underlayer, you never have to worry about that. Next, make a ‘Details’ layer. This layer will hang out right below the texmap layer. This where you put fine details like eyes, noses, and perhaps claws. If your animal has sharply colored stripes or spots, they can go here, or on their own layer. You can make separate detail layers for different colors of eyes, for instance, and quickly switch between them for comparison. Now make a ‘shadows’ layer, and a ‘highlights’ layer. These will be below Details, and above the Background. You will use these layers to adds darkness and lightness. Use layer transparency to allow the base coat to show through, and use the airbrush tool to give soft gradations of highlight and shadow. Experiment with darker and lighter variations of the background color for shadow, using the eyedropper and color wheel. By doing these on their own layers, you avoid messing with the background image. This allows you to erase the shadows and highlights entirely or using soft erasers, without erasing the background color as well. It makes it faster, in my experience, to get the shadows and highlights just the way you want them. It helps to use the selection box to select just the face you want to put the shadow on. The tool will not do anything outside the box, so you will have sharp edges. This helps show the box outlines, which can be useful from an organizational perspective, and if your texture is very packed, it may be absolutely necessary. Once you think you have it, make sure the texmap layer is off, and then export the file as a .png. Always keep a copy in your image editor’s format, so that you can still change things layer by layer. Nothing is worse than having details and shadows locked into a flat image, and wanting to change them. That’s the basic rundown - use a real image to get the colors right, add blur and noise for a whole-field background, and use layers to add details and shading. I leave the background covering the whole field, so I don't have to cut and paste bits of it around. This method does make it harder for someone else to understand the texture, if they don't have access to the texture map or model file. If you want to make this easier you can use the selection wand to select all the white space on the texmap layer, switch layers to the background, and hit the delete key, which will delete all parts of the background that are not actually in use.
  3. [0.2.4] TFC2 Prerelease

    The github for TFC2 hasn't been touched since June of 2017. Probably best to assume TFC2 is dead, and start pining for TFC1.12 port
  4. Leveling the cooking skill

    Not sure on salad vs sandwich. iirc there's no difference in skill increase with regard to size/quality of meal made.
  5. World Gen

    Personally I'm fine with things as they are. I know there was discussion on discord of getting rid of/compressing the bottom layer, and maybe even the middle layer. I think it'd be a mistake to get rid of the middle layer, but the bottom layer I could see going away. But to me part of the great fun of minecraft and tfc is the mining and exploring underground. TFC was flawed for a couple reasons: A) the cave-in mechanic made mining and exploring unattractive, because hidden caves would collapse as you got near them. So when you finally found them and broke in, it was a terrible landscape of cobble and destroyed ore. This was very not-fun. TFC1.12 needs to arrange it such that natural caves and overhangs have the blocks on the bottom set to not be vulnerable to cave-in, EXCEPT if the player is using powder kegs. Then all bets are off. That would allow the player to find the cave in it's natural state, and explore it. I don't know exactly how that gets done. In my mind, caves are 'hollowed' out of solid rock in world gen, so maybe every cave air block checks above itself and if there's stone there, then it sets a flag on that stone that it's 'caveroof', hence not subject to digging cave-ins, only blasting. Btw make blasting more effective. It was never as powerful as described in the TFC wiki. B ) The bottom layer offered nothing different from the top layer. The bottom layer needs to have ores that only occur there or occur there in much greater quantities, or with greater liklihood of the vein being rich. I would actually love to see lava not occur on the surface anymore, but only at the bottom of the world, in extensive lava caverns with extra-deadly mobs. This would make sulfur an actual resource of some worth. Diamonds could start as very sparse vertical 'pipes', similar to hot springs, but not a solid line. These would lead to the main deposit at the bottom layer. There needs to be a reason to go to the bottom layer, and there needs to be some more threatening mobs down there to make those resources more dangerous to get. Anything more above ground isn't of a lot of interest to me, because any ores up there are easy to get. Just dig them right from the side of a mountain. I've always found 100 blocks to be plenty of build height. All that said, I would totally support getting rid of the bottom and even the middle stone layer IF a mining 'dimension' is created. So at the bottom of the regular world, randomly scattered about at bedrock, would be portals that are made to look like tunnel mouths. These would teleport you to another dimension that story-wise is just deeper stone. It'd basically be the nether, but with regular stone rather than netherrack and fortresses. and such. Then you'd have an entire world of mining to do, and it could have even more unique mobs and environments. Giant mushrooms in the huge underground caves. The way the nether already generates is already great for an underground world, just replace the blocks. But get rid of the distance warping, and the tunnels between the regular and mining worlds need to be in the same locations in each world. And the nether ones need to appear at the very top of the mining world, in the upper bedrock. And btw, the tunnel from the normal world starts blocked. The player has to blast it open with a full barrel of gunpowder. And there you have an actual use for gunpowder in the game. I'd further suggest that if the mining dimension were a thing, that surface deposits be only poor and normal ore, with normal being much rarer - maybe 20%. And the mining dimension having the full spectrum of ores. This would give strong incentive to actually go mining and adventuring underground, which would improve the mod greatly imo. Edit: and I very much agree on swamps btw. I hated how they were just large ponds in plains in TFC. Bioxx was doing them much better in TFC2, where they were full of blocks in the water to make them harder to cross, and lots of reeds and willows. I really hope TFC1.12 makes swamps actually swampy.
  6. where's the kaolintie?

    Kaolinite is not y-limited as far as I know. I don't think any ores in TFC are.
  7. where's the kaolintie?

    Correct, sedimentary rock is top layer only. If your area has a non-sedimentary top layer, you'll have to travel till you find one.
  8. Food decay & preservation

    There was some interesting discussion regarding food decay yesterday on the discord, so I wanted to kind of compile some of it in this post so it doesn't get lost to discord history. It's been stated that TFC1.12 won't have the original tfc food quantities - it'll just use stacks of pieces as regular MC. Hence, there will also be no trimming. I don't think anyone will be sad to see trimming go. Basically 3 options are presented: The most obvious perhaps, would be ARK-style, where the top piece of a stack is always decaying on a timer. So if the normal decay time for vegetables is 5 minutes, after 5 minutes the top piece of the stack is removed. A visual changing of the background of the food icon indicates the time until next decay. This is what TFC2 was going for in the last iteration, and it's a pretty well known system I think. @Bunsan presented another option: "The thing to remember is that in 1.7.10 it did not care how old the food was, it just cared how long since last trim and how much decay is present. So that is effectively the same as having each item have a set chance to decay and then have it roll to decay every X number of ticks. Whether it just goes poof or turns into a decay item doesn't matter." So basically that seemed to be suggesting that every piece of food in the inventory has a chance to decay every tick. Which has the same statistical result as Ark style probably, in that statistically, per time period, you'll lose just 1 piece. Sometimes maybe a bit more, sometimes less. But statistically same result. There's no icon background timer in this method, so on the one hand you aren't constantly nagging at the back of the player's mind with a visual reminder as each piece of food disappears. But at the same time, it's a somewhat less predictable system. Some people may actually appreciate the defined rate of decay in ARK style. @TonyLiberatto presented another idea. As I understand it, his idea is that when you harvest or create food, it is marked with an 'expiration date', which presumably will show in the tooltip. Expiration dates are only to the day, not the hour. So a carrot harvested at 1am of a given day will have the same expiration date as one harvested at 11pm. Stacks of the same item with different expiration dates would not automatically stack. When the stack reaches the expiration date, the entire stack vanishes or turns to rot or whatever. SO in this system there is no constant drip of food disappearing. You have it all available until the expiration date, and then it's all gone. This is arguably a bit more realistic in that for most food, it does not immediately start having parts go bad. I don't know if maybe it has some processor overhead advantage, in that you'd only check the food once a day, at a certain time, rather than having to check every X ticks? The more I think on it, the more I like Tony's system, and I wanted to expand upon it a bit. I think you could still allow manual combining of stacks to avoid too much clutter, but perhaps just inherit the lower expiration, to avoid hijinks with averaging. This way the player can choose between less space used, and keeping a higher expiration date on some. This also opens up a possible avenue for containers that are food-specialized, having many slots but only for food (in some cases maybe just certain kinds). These containers allow the player to store many stacks of food with different expirations. I also think this system might discourage people like me, from leaving crops in the ground forever in non-freezing climates and harvesting them when needed (though hopefully that won't be a thing anyway) since that would probably result in either more clutter or more wastage, vs. harvesting large amounts at once and properly preserving. Another possibility I think expiration dates would open up, is for there to be food poisoning effects. So your food is safe for some percentage of it's life - maybe the first 50 to 75% - but thereafter the background color changes (maybe to orange) and you get an increasing chance that if you eat this food, you'll get food poisoned or catch a disease or something. Preserving the food might nullify that chance (the background is normal all the way to expiration) or it might delay it (only turns orange at 90% of expiration, and also the chance does not get as high due to reduce poison window). You could even do a sort of hybrid system. Maybe the food doesn't decay for the first 40% of it's expiration date, but upon reaching 40% it gets orange background and starts to decay ark style or random style or whatever, but still no poison chance. But at 70% of expiration it turns red, and now it is not only decaying, but you also have the poisoning chance. So there the player gets a window with no decay, but then there's a significant window with decay, and at the tail end poisoning. So ya, in the end I rather like Tony's system and think it presents some good hooks for other mechanics.
  9. Is there still development?

    Original TFC (v1.7.10) is dead. Bioxx had started to develop TFC2, but that is in limbo now, and also it's rather different from original TFC. Some community members have taken it upon themselves to make a 1.12+ version of TFC, but that is in a very early stage.
  10. Food decay & preservation

    Yes that's correct, in one of the final versions there was a config. And yes, of course they die in cold weather. There was a pretty significant swath of the world though, which never froze, and was easy street as far as food goes. In practice I think servers is where you *want* immortal crops, due to time passing while players are absent. So they were the least forgiving. But there's other options. You could have crops simply start over again when they reach a certain age. That would make them a little less reliable in mild climates, as far as an easy-mode ready to go food source.
  11. Simple "playability" changes.

    Well, a true feast or famine is like rock salt or flux stone. You have 0, or you have an infinite amount. So it goes from being that valuable commodity you want very badly, to being an infinite commodity that is essentially value-less. This is bad for the game regardless (imagine if you could find entire biomes of copper or iron). The clay situation in 1.7.10 isn't truly that, it's just a resource similar to others - present some places, not in others - but the immediate starting need means it shouldn't be entirely missing in large areas, except maybe deserts. Even a newb could pretty easily logically come to the conclusion that deserts don't have clay, and decide to either accept the challenge, or roll a new world. It is nice to know there'll be some 'out of the box' server options built in this time. Please build in some kind of merchant support!
  12. Food decay & preservation

    Ya, that was actually another discord topic. Bunsan Had a question on peoples' thoughts on the temperature gradient and in the course of that it turned to how it affects preservation. I am of the opinion that being able to infinitely preserve food simply by storing your food in an environmentally cold area makes other preservation methods less useful, and so hurts the potential preservation tech tree, and that I'd rather see ambient temperature not affect it at all. Counterpoint was that on servers it's good to have a no-maintenance permanent preservation, due to possible extremely long times passing while player is offline, and that's a good point. Eventually I suggested something like what you propose gcook. Basically that items stored at freezing temps eventually become "frozen", and in that state they cannot be eaten, and the stack can neither be combined nor divided. In order to use the food the player must defrost it, which takes an amount of time commesurate with the stack size. So the player now has a choice of whether to store efficient giant stacks of food that take forever to defrost, or many small stacks that they can defrost and use quicker, but that take a lot of storage space. If you've ever tried to defrost a big turkey or ham, you know it takes days. I'd suggest a stack of 64, for instance, take 4 or 5 days (2 hours per unit?). This allows the player to still have simple infinite cold storage, but requires better planning to use it. I further suggested that every time you thaw a stack, some portion of it is lost to 'freezer burn', as a deterrent to repetitive freezing and thawing. The minimum loss is 1 piece, so the smaller the stack thawed, the greater the percentage lost, which plays into the choice of freezing in large slow-thawing stacks, or small fast-thawing but high percent loss stacks. To go with this, you'd have a 'chilled' tag or something, and this would get applied when the player uses 'constructed' cold storage that is part of the game progression - for instance ice boxes or ice houses or refrigerators, etc. chilled items would be useable immediately, rather than having to be defrosted. Items that are neither chilled nor frozen simply don't have a tag. Immortal crops are the other big killer of preservation use, but that's a separate topic, and more easily addressed I think.
  13. Simple "playability" changes.

    Oh I agree about the exploration and the search, but I'd suggest that the resources that you need basically day 1 are not great candidates for complete exclusion from entire biomes. I think upper tier ores and such are much better for that. Reducing dry biomes is a possible way to address the clay factor for sure, though I'm also kind of hoping deserts are more common and extensive. Is it possible to prevent the player from spawning in dry biomes? If selected spawn rainfall is below X, select a new spawn? Difficulty levels where the player can choose to start in a harder starting biome if they want? Or at least a popup if the player starts in a dry spawn, that explains to them that they won't find clay in the biome?
  14. Submit Questions for FAQ

    - Will there be mining collapse? If so, will it be fixed so that natural caves don't collapse? This really killed the fun of caving in TFC1. Also, will the collapse mechanic be simplified so that collapses that start outside the supported area don't propagate into a supported area? This function frustrated and confused many people, and I know that there are people who specifically dropped the mod because of it. - Will clay be fixed so that at least some occurs in dry biomes, so that you don't end up with newbs confused why they're not finding clay in their spawn area? @Bunsan Hopefully these do not come across as 'suggestive' FAQ questions. I do think it's very relevant to a great many people, who may have dropped the mod because of some of the very poor design choices in TFC1 (feast/famine resources) but also some who just have preference differences (collapse mechanics). I do understand if you delete my response to Dries re: flux.
  15. Simple "playability" changes.

    The old clay situation makes for a poor gameplay experience for new players. I watched a great many lps of people who started in dry biomes, and they're hunting around for clay, not understanding why they can't find it. These kind of feast/famine mechanics are just bad game design - it's the kind of thing that turns new players off. Mia's idea of having limited clay deposits even in dry biomes is a good one, and I would definitely vote for it.
  16. Does this forum have to be dead?

    https://www.reddit.com/r/tfcplus/ Basically dunk is taking 1.7.10 TFC and making some relatively minor changes. The upside is it's playable now I think, since the changes are minor. However in the long run, if the 1.12 port succeeds, I think TFC+ will end up obsolete.
  17. Submit Questions for FAQ

    The simple way to fix flux would be to have borax appear anywhere. You could also have potash (as a very inferior/time consuming flux perhaps, since it'd be relatively easy to get).
  18. Submit Questions for FAQ

    A couple questions regarding fixing of TFC1 mechanics, will flux perhaps have several sources, or otherwise be modified so that it's not a feast-or-famine situation? It really does not benefit the mod to have the player have either 0 flux, or more flux than they will ever need, with nothing in between. Also, will alloying be fixed in a way such that if you're for example mixing copper and cassiterite, and you add some already-made tin-bronze ingots, you don't ruin that batch? Incompatibility between a mixture of ingredients and already made ingots of the same material was one of the worst things in TFC1, especially when it happened for colored steels.
  19. TFC1 1.12+ port

    @Dries007 How about mobs? A team of us made quite a few for TFC2, but I'd imagine those models can be just as easily used in this project. Though I like TFC2 worldgen much more than original (any plans to change that at all?) and still wish it was an active project, I'd rather see those models used somewhere than not at all. I always felt that a stumbling block was the animation. Bioxx put together MCMC which made it easy for us to make the models, but it was still up to him to animate them, and so I think that naturally always played second fiddle to the more 'core' aspects. As I understand it animation consists simply of applying a rotation range, and timeframe in the form of a cosign or something, to a part. Is there any chance at all that that could be added to MCMC at some point? This would allow non-coders like myself to figure out the correct numbers to use to look good, and probably save coders a lot of trial and error.
  20. When can we play tfc2?

    When minecraft finally updates to 1.13, we'll find out. The 1.13 update changes huge amounts of code, so it's not unreasonable to think that Bioxx would go on hiatus until it is finalized, rather than do a ton of work that he'd have to do over when 1.13 dropped.
  21. TFC2 Food and Other Stuff

    As i recall (don't have time to search for the old threads) Bioxx was not committing to the final food situation. He said Pam's saves him a ton of work for now, but later *maybe* the situation changes. As for features, I don't know why it wouldn't. TFC1 didn't really have all THAT many features.
  22. TFC1 1.12+ port

    I think that's a very good choice. It did seem to cause a lot of problems with mod compatibility, for not much gain vs a decaying stack.
  23. Physical Smithing

    Your suggestion would get rid of the random seeded nature of smithing though, correct? Personally I find that one of the interesting aspects of TFC smithing: you kind of have to re-learn your smithing for each new world.
  24. Do you check the forum everyday?

    The minecraft 1.13 update is, from what I understand, unlike any other update. It is entirely reworking most of the 'guts' of minecraft, in order to allow unlimited block ids, amongst many other things. This isn't just a matter of changing combat, or adding some mobs. The sticking both hands in up to the elbows and messing about. Why should Bioxx do a bunch of coding before 1.13 comes out, only to have it mucked up and have to totally redo it in 1.13? They've already started to do that once for the 1.7->1.8 transition. Why do it again? People who haven't taken a good hard look at what is actually involved in 1.13 need to go do so. It is not trivial, not even remotely. All that said, I do not have any insider knowledge, and for all I know Bioxx has won the lottery and is living it up in Malta. We'll see when 1.13 drops, hopefully early next year.
  25. Adamantine

    Really though, that's a good argument for having it at depth - to give incentive to mine deep. But as to the OP, I'm not really that wild about copying DF so directly. And I was never a fan of DF's weird canon regarding the fibers. I would say adamantine should be found in small pockets at the bottom layer, in close association with lava, possibly even mostly below lava, with just a small tip sticking above, like an iceberg. I think that there should be a new source block - magma. Magma should not be able to be deleted by block placing or water. It should require special machinery/magic to remove it to allow access to the adamantine below.