Minecraft Forums

Quote from PengoPenguin

I'm not entirely sure, all i know is that the after building the light nexus pillars the nexus rune doesn't show. I figured I missing a step.

The rune is made with chalk. In the case of the light nexus, you need to make white chalk, and place it in the very center of the nexus. It's not something that automatically appears when you've got the structure right.

Chalk should always be able to place a pattern, in a 3x3 square centered on the block surface you click on. If you can't, the terrain may be unsuitable. You can place chalk before or after the rest of the nexus structure.

If you have chalk on the ground, the sign that your nexus is complete is that the chalk pattern will start turning in place. At that point, a light nexus will accumulate energy naturally and the other two will be ready to do so when their respective resources get close.

If you have the pattern down and the structure in place, and it's NOT turning, it's possible that you have the wrong chalk. White for a light nexus, blue for essence, red for dark. IIRC from the Compendium purple chalk is used for something completely different.

Quote from druha

Well now that you know about it,and don't like it, you could turn it off in the config:

# Negative nodes like hungry, tainted or dark nodes will have additional, much nastier, effects.
B:hard_mode_nodes=false

But the behavior of the other nodes doesn't seem bad enough to justify this. Creates a bunch of monsters at night? Those can be dealt with - or if they're overwhelming, it's still something that leaves the player agency. Generates taint? It's possible to contain that - and, again, even if it proves lethal, it's still something that gives the player a chance to try to survive it. Still-nastier effects that I haven't seen? So long as they give me a chance to respond, that's fine. I don't mind the nodes being dangerous - what I do mind is a guaranteed death trap.

One point of information that I was not aware of, and which could stand to be added to the Thaumonomicon, is that aura nodes are fragile things and can be disrupted by the direct application of force - which is to say, that they can be broken by hand. Knowing this, my biggest gripes with hungry nodes are reduced to a combination of two things, each of which seems to be buggy behavior:

First, when I was grabbed by the node, my view kept getting yanked back to a particular direction. I would not have been able to aim at the node.

Second, the force of the node kept me very rapidly oscillating over it, so even if I'd been able to look around, it would never have stayed in my crosshairs long enough to do anything with. (I suspect this is related to why I got flung upwards - the motion built up in a manner like resonance, and eventually exceeded the limit of the node's own pull.)

If I'd been able to look around, and if the node had pulled me to its location horizontally but kept me under it, I would have been able to recognize the problem and break the node. Bam - player agency restored. If breaking a node has negative consequences, so be it - it still leaves the player with agency. The lack of agency is the core of the problem here. Restore agency, and I'm willing to put up with the node being dangerous - indeed, I would rather have the nodes be hazardous than turn off all those hazards because one of them is seemingly broken.

Quote from IStoneI

dont go too close to hungry nodes then. they are very well visible, by the flying blocks and the destruction they cause around them.

If you think the broken terrain around such a node is unique to them, I have to wonder what game you've been playing. I didn't even see the node the first time I got flung around by one - thought it was an Ars Magica air elemental or something. Even the second, by the time I was anywhere near close enough to the node to actually see the damaged ground under it, it had grabbed me.

As for items flying around, I saw none such. When actually grabbed, I could hear blocks being broken, but they didn't seem to be generating loose items - certainly not enough to be visible in terrain with any kind of brush. Of course, the fact that even my vision was trapped and kept getting pulled back to the same angle didn't help matters on that count.

lava pools are surface gen too, and you dont jump into one of those.

Lava pools are obvious and utterly unmistakeable (unless the lighting bugs out around them, at which point they can suddenly become much more threatening for not being as obvious). To anyone with full-color vision, they look like pools of fiery nastiness. Even without that, they have smoky sizzly particles around them. You couldn't really have a more obvious "don't go here" sign this side of actually writing it out, if that. Irregular terrain could just be irregular terrain, or it could be a sign that there's a tunnel. Far from the obvious danger, here you have something that could actually draw people in.

as for being flung into the air, the harness should help. but i was under the impression, that these nodes actually eat you. been drawn in by one of them, when i got too close and took damage until i died, instead of being thrown into the air.

The question of damage was odd. If I happened to be morphed at the time, say to a bat, I took damage until I got flung. My SO was not taking damage without being morphed, though - nor getting flung. I thought, thus, that the problem might lie with morph, unmorphed, and got killed for it.

Now, Morph makes flight accessible - too much so, it can be argued not unreasonably. But the thaumostatic harness is not only late-game research, it's not something I'd be just wearing around the wilderness; I would have it on when I expected to need it (for construction in high places, for prospecting a canyon wall, for boss fights that warrant it).

Your statements reflect ideal conditions: you are alert to the danger, you are prepared for exactly the consequences it can inflict upon you, and most of all, you know in advance what it is. Try muddying the waters somewhat: you're on a fairly new world/character (no harness, no goggles), it's getting dark, and you're trying to avoid getting murdered by machine-gun skeletons. And you don't know these nodes exist.

Making the nodes exert force on the player would be one thing. It'd make them a hazard if there are hostiles nearby or if they pulled you towards dangerous terrain. Even having them harm you while you're nearby would not in itself be intolerable - but only if you have a way to get free. As it stands, they are an inexorable death-trap which it is far too easy to stumble into unawares. Some people think that's great (see also: the Tomb of Horrors), but it's not something I want in my games and is a major tonal shift from how TC was before.

I dislike the nodes as they stand (or at least, as they worked when I encountered one) for much the same reasons I despise EBXL's version of quicksand: they're both trial-and-error gameplay that rewards new players exploring in an exploration-heavy game not only with the already-painful consequences of Minecraft death (which they get to sit and watch happen, to boot, utterly void of agency), but then slaps them in the face by destroying everything they own without even the usual chance of recovery.

All for the terrible error of not being prescient.

That might be fine for people who favor Hardcore mode, but Minecraft isn't only made for those people.

It's been answered before, but to recap, you need a force flask. Hit a Creeper with a weapon a few times to weaken it, but don't kill it. Then hit it with the flask to bottle it while it's weak.

It will blow up in the bottle. This will treat you to a point-blank explosion, so be healthy and ready for it; but it will also give you glass powder.

Quote from zentag

um mydio did read that thread. He may not have used some suggestions but he read it.

It's not merely a lack of acknowledgement that leads people to think he didn't:

Quote from mDiyo

Guys, please keep suggestions on the suggestions thread. Posting them here clutters the thread and is likely to make me angry.

..and no, I don't read the suggestions thread.

Quote from notfood

That's a huge lie. It just requires a couple of lines changed in Metalurgy code. No idea why they are choosing not to do it. It IS a bug when Metalurgy isn't using the proper Forge calls to register ores in the dictionary. I can point which line in the decompiled code needs to change.



I know how you feel, I did the same.

I wrote my own forge mod and called registerOre in TConstruct manually for each Metalurgy ore.

// for copper assuming Metalurgy copper id 26507
TConstruct.events.registerOre(new OreDictionary.OreRegisterEvent("ingotCopper", new ItemStack(26507, 1, 0)));

And so on for each metal I want in the smeltery. I guess I could make it read those ids from Metalurgy config file but eh, it was just a quick fix.

Not that I know even enough Forge modding to accomplish that myself, but... does that need to be done manually for each ingot, dust, AND ore? Yeouch.

But yeah. There's a major difference between full support for all the Metallurgy metals and alloys in TConstruct (which only needs unique sprites for each combination of metal and part if you insist on making it so, so the 5000 number is probably a misleading, drastic overstatement when most can be recolored) and making the ones that already overlap compatible.

There's a recipe conflict with the newer versions of Tinkers' Construct; one log atop another is suddenly yielding TConstruct barricades (oak, if it doesn't find a more specific match). TC has moved to 1.6 full-time (says the changelog). If Dartcraft sees any final updates for 1.5.2, is there any chance of allowing some alternate recipe for force sticks? Maybe side-by-side/shapeless? I know it's not as intuitive given the vanilla stick recipe, but it would get around this conflict and allow the mods to coexist.

If not for 1.5, it might still be useful going forward.

"Other part casts must be created by pouring metal [alumi brass or gold] around existing parts, like a pickaxe head, or on the wooden pattern."

Am I the only one who couldn't get the latter to work? I can make casts just fine by casting around the part(although I almost wish it destroyed a nonmetal part in the process), but putting the wooden pattern on the casting table, then trying to pour gold/brass over it, did nothing. Only when I gave up and made the part could I get it to actually work, which was a bit of a pain for the T2 parts.

I love the look of the Nether stuff (complete with new crafting tables/bookcases!), but I'm running into a problem of note: it seems that Natura's Nether worldgen is no longer quite recognized as Nether. There is no bedrock ceiling (just a mostly-flat expanse of netherrack except where I had already been in the Nether with the prior version of Natura), and things which normally spawn only in the overworld (like Ars Magica towers) can suddenly appear in the Nether, complete with dirt base and/or overworld wood, and on one such spot I even got an overworld hive from Extra Bees. There are no such collisions in the old worldgen.

Also, I'm not sure if it's related because I don't go there often, but ever since updating to the new Natura, I've been unable to go to the End. It sits on "Downloading terrain..." forever, with the only message in the log being that it's loading dimension 1. No crash, no console output of any kind; it just... sits there. Using MultiMC to generate a crash log doesn't reveal anything different than that unhelpful console log. I've had difficulty pinning it down as definitely Natura, but the mention I saw above about clouds in the End makes me wonder if in some configurations (e.g. with Ars Magica?) it's putting worldgen into an endless loop. Is there any way I could try to force Minecraft to cough up more information on what it's doing, so I can be sure I'm directing this problem to the right place?

Quote from Kazekai

Do you think it could be possible to dye force bricks with vanilla recipes, or something added by the mod itself? I'm not too big on IC2...

This would be nice. Just as force bricks can now be crafted, it'd be nice to do the same with dyes - say, eight force bricks of any colour around the dye of choice. (I think this is most readily accomplished by way of the ore dictionary, making all force bricks a "class" of item, but not sure of that or of the proper wording. At any rate, having a single recipe for each dye, rather than needing one recipe per colour of ingredient per product, would be a LOT simpler all around, and allow for odd bricks to be used.) Yes, it's less efficient for dye than the painter (8 bricks coloured vs 32), but it's convenient and doesn't require IC2.

Quote from Shurhaian»

Regarding the researches, I'm admittedly not sure if they're hidden or just invisible until prerequisites are researched, though I've researched enough that I'd hope the Urn would be available by now, to say nothing of the seals. If they are hidden research, their status as such should be carefully considered, and if they stay that way, the icons adjusted to suit; if not, having some more "echoes" of prerequisite research pointing into the Thaumic Esoterica tab, rather than have things be completely invisible, may be nice to get some direction. Or at least have the ThX stuff show up. (I don't mind Forbidden Magic's emerald transmutation having a non-displayed prerequisite, for instance, since it's not all that hard to tell what you need for it and it's not a very deep research.)

That would be a B:requireLeafDecayCheck=false ? Trying that now....

...and did not work.


Or wait. Did I put it in the right place? Probably not. INSIDE the coloredtree{} definition, I'll bet. Retrying.


...And success!

    projectred {
        S:axeIDList=<item:peridotaxe>; <item:rubyaxe>; <item:sapphireaxe>
        S:blockConfigKeys=block:block_dyeLeafID
        S:configPath=ProjectRed.cfg
        S:itemConfigKeys=item:peridotaxe; item:rubyaxe; item:sapphireaxe
        S:modID=ProjRed|Exploration
        B:overrideIMC=false
        B:useShiftedItemID=true

        coloredtree {
            S:leafConfigKeys=<block:block_dyeLeafID>
            S:logConfigKeys=17, 5; 17, 13; 17, 9; 17, 1; 17, 4; 17, 12; 17, 8; 17, 0
            B:requireLeafDecayCheck=false
        }

    }

I think the heavy material costs in exchange for the time, luck, and exp investment does a fine job of being an alternative to vanilla enchanting. The only balance problems I see are the Rapier, maybe the Dagger, and overabundance of materials due external influences. Quarries and Frame Bores can make ANYTHING feel cheap... except for enchanting since automation usually robs the player of sources of exp. For anyone using these (Feed the Beast IS really popular right now), of course the Tinkers' tools are going to feel dirt cheap compared to enchanting, and pre-established worlds are going to make them feel dirt cheap as well. That's improper use of the mod, the fault of the player, not some inherent flaw in the mod.

To clarify my two other points though... I really can't think of a situation in which the Dagger would be useful. Someone explain to me what I'm missing here, perhaps? As for the Rapier, it's the combination of armor piercing and the complete lack of a hit cooldown.

It's a pretty safe assumption that players will at least be wearing Iron Armor, though in any modded game, Diamond is probably the better assumption. Even more so considering Manyullyn armor is a strong likelihood. Ignoring enchantments, Iron reduces incoming damage by 62.5%, and the full bar from Diamond reduces incoming damage by 83.3%. (At least according to the wiki.) With the assumption of Diamond Armor, other weapons would have to do 5 times the base damage of the Rapier to come close to evening out. Yeah... under no circumstances does that come about (the Iron assumption isn't much better), nor would that be a scale that would be very feasible to pull off in a rebalance. Armor ignoring is an issue at its core. Now, one might argue that these weapons are not designed for PvP and thus should not be coming up against such high armor values, but why cut out such a chunk of the potential demographic of the mod? And what about mods that add creatures with higher armor, such as bosses? The point of this mod is variety, is it not? So no one weapon should be ideal, else it hurts that variety.

The lack of a hit cooldown is far less of a problem where any PvP is concerned as other sword users will be capitalizing on knockback and thus help neutralize this advantage. This one is more of a "PvE" or general gameplay concern, and it's a glaringly obvious one to boot. Consider for a second that one can easily attack a mob three times in the time they would normally be invincible from the previous attack. Consider further that even five attacks in that time is feasible. Rapiers when spam attacked can thus deal 3, 4, even 6 times the damage. Are Rapiers 3 times less powerful than the Broadsword? ...nope. This design scales damage to an out of game factor in how fast a player can spam the mouse button, rather than cutting the period of invincibility down to a particular fraction and balancing accordingly, and even if the faster players are ignored, the number of attacks are enough that other weapons just cannot keep up. Again, one could argue that the damage boost from sprinting with the Longsword is a rather tempting option since it is more defensive as well (unless your target happens to be a Skeleton, Witch, Wither, or any other ranged or immune to knockback enemy...), however the Rapier happens to have that very same bonus and of course can squeeze in multiple hits in the moment before the mob flies back. (I do this even with normal Broadswords; it is a simple thing to do.)

But what about the defensive option of the Broadsword? Surely one would still want to use that. You'd think that, but no. In PvP, the enemy's Rapier doesn't care about your attempts to block, and in most melee scenarios, hopping back and just not getting hit is preferable to attempting to halve the damage you're guaranteeing you will take. If there's something hazardous behind you or if you can't time it with a Skeleton's shot, sure, you could get use out of a Broadsword by... using it solely as a shield rather than a weapon, but the Rapier has by far the most powerful defensive ability of all. No, I'm not referring to the hop back this time. I'm referring to the lack of an attack cooldown. In combination with Necrotic Bones, specifically. Unless you're entering a place where there will be predictable volleys of ranged attacks that you won't be able to avoid, you are far better off using a Paper Rapier with 1 Diamond and a bunch of Necrotic Bones as your "defensive weapon" than a Broadsword, because you will be landing hits as fast as you can click, and you will be healing 5 "hearts" with every one of those attacks until the enemy keels over. 6 with a Diamond and Gold Block thrown on, 7 with a Nether Star added as well. Who needs blocking when you get the equivalent of a healing potion with every click of the mouse?

I love this mod, I'm excited at its growth, and I can't wait to see how its features evolve... but something aught to be done differently about the Rapiers. No other choice compares to a Manyullyn Rapier and Paper Rapier on your hotbar, and that's not speaking from preference. mDiyo, in your excitement to give them unique mechanics, you went overboard, plain and simple. Can you perhaps rein them in a bit, please? Give it a far smaller percentile boost in both effects, perhaps? Maybe put a cooldown on how frequently Necrotic Bones can trigger?

And if anyone wants to pipe in that it's about fun and not mathematics, and that "balance" is a fictional construct, and people shouldn't dictate how others play the game: let's try something, hrm? Go watch Direwolf20's and SOTMead's videos on Forgecraft 2 and tell me what weapons you see the various testers and the like use.
Then explain to me how absolute supremacy and nigh universal preference is a good thing for a mod that otherwise tries so hard at providing variety, options, and customization.
I'm sick and tired of such literally thoughtless arguments whenever/wherever someone brings up a balance concern. (This segment is obviously not directed at anyone who doesn't present such a viewpoint, of course.)


I apologize for the extreme wordiness of my post, but I did not want to make a balance "complaint" without making sure to thoroughly back it up. No one wants a crash report without the log; why should I bring forth a complaint without all the relevant details. ...right?


Oh, and you seem to have made grass spread under relatively shallow water with your "clear water" change, even with making it client only. That's definitely effecting how light behaves with water mechanically, rather than just a visual tweak. Unless this is intentional, you've got a bit of a bug there. Personal preference to me, though, would just be to get the visibility bonus from a helmet modifier equivalent to the Respiration Enchantment and have it serve as a proper parallel, as the weapon and tool modifiers tend to be.

Following up to my previous post...

All of the UE mods are working in MC 1.5.1. Well, I haven't tested their operation yet, but the game loads with only two ID conflicts (@ 1 and @ 31743 - talk about being at opposite ends of the ID spectrum, haha) that I haven't investigated yet. Maybe they are supposed to overwrite those IDs. All I have set up so far is MC 1.5.1 + Forge 662 + LWJGL 2.90 + All UE mods using either the recommended build if there is one or the latest build if there is no recommended one.

Home-made 1.5.1 Ampz pack here I come!

(Screenshot of my mods folder if anyone needs it)