Hi. I'm trying to use this mod in 1.7.10, but no structures.ruins will spawn in. I'm stupid when it comes to modding so I don't know what to do. Can someone help me with this, with photos showing the steps to fix this?

In reply to gio52903:

 I am having the same issue. Does anyone know how to fix this?

Edit: I fixed it. What you want to do is open the file it downloaded, open the "mods" folder inside, copy the jar file at the bottom, and paste it into the mods folder. you should delete the rest afterwards.

 My second question might have gotten lost, so I will ask again, hopefully someone knows? The structures will only spawn about 400 blocks from the original world spawn point. I have actually mapped it out here The small red circles are the structures on the outer ring of the spawn area. Is there a way to change this so it creates structures no matter where you go? I know it did it in 1.12 but for some reason it will not so it in 1.15. Thanks!

In reply to InsaneTala:

The first thing I'd do--if you haven't done it already--is check the RuinsPositionsFile.txt file in the world folder to make sure there really isn't anything outside the circle.

Assuming there isn't, the most likely culprit is Ruins stopped working at some point. Maybe an incompatible mod was added, maybe a file became corrupted or inaccessible, maybe there's a bug (though I'm not seeing this behavior in my test world). There are any number of possible reasons, but you should find clues in the log file. Search for error messages coming out of Ruins or at startup.

Less likely: Ruins can be configured to confine its structures to a certain distance from spawn. Look at the ruins.txt config file in the world folder (not the one in the config folder) and see if the parameters anySpawnMinDistance and anySpawnMaxDistance are set to something other than their default values (32 and 0, respectively, where 0 means no limit). Each individual template also contains a spawnMinDistance and spawnMaxDistance parameter specific to it, but I suspect these are rarely used.

While you're looking at config parameters, also check templateInstancesMinDistance. The default value is 256. That's the number of blocks you'd have to travel before there's a chance to see another structure from the same template. If it's a particularly large number, you'd expect to see exactly what you're seeing: each template will produce one structure fairly close to world spawn, and then no more will appear until quite a distance away. Again, each template has its own uniqueMinDistance parameter, too, with the same effect.

That's the most I can suggest with the information provided.

In reply to QuarterAnimal:

This is the ruins.txt in the world save. Apparently the anySpawnMaxDistance is only 500.

 # minimum distance a template must have from instances of itself
templateInstancesMinDistance=256
# minimum distance a template must have from any other template
anyRuinsMinDistance=32
# min/max distances overworld templates can have from world spawn (0 = no limit)
anySpawnMinDistance=32
anySpawnMaxDistance=500

To which, I believe I have corrected in the Ruins.txt in the mod folder? I hope I did that correctly? XD If this works, THANK YOU!!!! I have been pulling my hair out trying to figure this out!!!

EDIT:

IT DID WORK YOU ARE SO AMAZING THANK YOU!!!!!!

In reply to anger_alfaro:

Yes...but there's a potential catch. There's always a catch.

Ruins is, for the most part, only involved with the population of new chunks. Once a structure is placed in the world, it's just another regular bunch of blocks. You can, therefore, update your world without installing the Ruins mod, and everything should be just fine. Already-generated Ruins structures will still be there, but no new ones will be created.

Here's the exception: Ruins provides a special RUINSTRIGGER directive template authors may use in their command blocks to delay execution until an entity wanders nearby. If you have unfired RUINSTRIGGERs in your world without Ruins installed, those commands won't function, and the command blocks will remain intact.

If the string "RUINSTRIGGER" doesn't appear in any of your templates, or if you can live with a few command blocks lying around, you've got nothing to worry about--update and live your 1.16 dream. Otherwise, it's still not a huge deal; you can still update, but you may need to do a little creative-mode cleanup to get rid of any pesky untriggered command blocks

Is there a way to blacklist specific biomes so that no structures spawn in them?

In reply to TheVisionaryOne:

No. However, if you moved or deleted all the templates in the generic/ folder (a good idea in general) so that it's empty, you can set the biome-specific template selection probability for the biome(s) you want to blacklist in the ruins.txt config file to 0 and achieve the same effect. For example, if I want to prevent Ruins from placing structures in flower forests, I'd set:

specific_flower_forest=0

That means Ruins has a 0% chance to select a biome-specific template in flower forests, and therefore a 100% chance to select a generic template...but with no generic templates, nothing gets built.

In reply to Jiggly_Bear:

It's not really an error, at least in the sense something is broken. Unlike vanilla Minecraft, Ruins doesn't do procedural generation (long story). In order to process a given chunk, some of Ruins' features may require the mod to "see" adjacent chunks, forcing them to be also be populated or loaded. Forge recognizes this situation as potentially troublesome and flags it in the log file.

While there is some lag as a result, it's typically slight and not a problem. However, if you have very large Ruins structures, templates spawning other templates, a configuration producing very dense placement, or a server with lots of players, the lag can become severe. Just ignore the log message...unless you're experiencing dramatic lag spikes, in which case you may need to prune the offending templates.

What would one add to ensure that a particular ruin only generates in the overworld? I see the "dimensionsToSpawnIn" part of the config, but which format would I write out the overworld dimension?

In reply to rsleeezy:

The values corresponding to vanilla dimensions are overworld, the_nether, and the_end. So, if you want to specify a template should only occur in the overworld, simply include the following line in its .tml file:

dimensionsToSpawnIn=overworld

A few things to note:

• If dimensionsToSpawnIn isn't specified at all in a template, or there's nothing after the equal sign, it defaults to all dimensions (vanilla and modded).
• Finding the name corresponding to a modded dimension can be a challenge. If you're lucky, you may be able to find it in the log file. Otherwise, it requires digging into the code, using a utility mod, asking the author…or reading the comprehensive documentation that totally exists for every mod, amirite?
• While the current convention for most Minecraft names is to use only lowercase letters, digits, and underscores, no restrictions are enforced. Modded dimensions, therefore, may have pathological names, non-unique names, or even no name at all. Ruins may not be able to fully support such unconventionally-named dimensions.
• Ruins is especially fussy with regard to parsing template files. In particular, make sure there are no spaces anywhere on the line (unless you're including a modded dimension with spaces in its name), else it may not be doing what you think it's doing.
• A technicality: what I'm calling "dimension" here is actually "dimension type" (or, to be even more pedantic, DimensionType). The distinction only really matters if you're looking at code, though; for everyone else, referring to "type" would likely be misleading—despite the name, it's an identifier, not a category. I'm just mentioning that here for completeness.
• There's an allowedDimensions parameter in the config file ruins.txt, useful for wholesale enabling/disabling Ruins in certain dimensions. Unlike the dimensionsToSpawnIn template parameter, allowedDimensions refers to dimensions by number instead of name, as these are server configuration items. The default is allowedDimensions=0,1,-1, which corresponds to the three vanilla dimensions (0 is the overworld).

In reply to QuarterAnimal:

 Awesome, thanks a lot. This really helps.

Can we please get a 1.15.2 version please? Im using GD Launcher to install mods, and since there is no official 1.15.2 version, GD Launcher isnt picking up the 1.15.1 version...

why isnt my config folder not showing up in config, and in agme no structures are being spawned. why is this?

 This is amazing! I hope this mod will grow to have thousands of available structures to be generated :) :)

Quote from manowin >>

Hi there,

i love the ruins in the 1.7.10 version of this mod. Is there a way to get them in a package for a 1.12.2 version? I tryed by myself to add the old (ehm tml?) but it does'nt work...
So know i must accept... that i need help...

 

My wife and me are big fans of the 1.7.10 ruins... we hope for someone who can help!!!

greetings!

Mano

 
Hey there, is there any way to get an answer? I hope, because i miss the ruins of 1.7.10 so much! BR mano

In reply to manowin:

 would be great if you or someone else might get the old mod onto version 1.12.2.

Greetz
Bockiskitchen