squeek502 / creativeblocks Goto Github PK

I have an issue with the default list. It is always in effect. I wrote up my own list and still the default list was in effect with my list. I tried changing the name of my file to default but the mod just rewrote the default one.

/creativeblocks <player> would put the specified player in the creativeblocks gamemode. This is intended for servers where not everyone wants the mod enabled. So basically what I'm asking here is that players that have /gamemode creativeblocks enabled would be able to use this as intended while not affecting everyone else. The blocks placed by those in /gamemode creativeblocks would be breakable for people not in the gamemode, however, they wouldn't produce a drop.

I thought of this idea when designing new gamemodes for my server like /gamemode magic, /gamemode tech. /gamemode magic would force you to only use magic mods and the same for /gamemode tech.

If it cannot be done then, oh well. Thank you squeek502, I love this mod to no end and would like to enjoy it on my server as well without affecting others.

It's super annoying to have to keep running around fixing my base since I'm so clumsy and keep bashing holes into walls and floors. Just removing a machine or other block in a room made of creative blocks can be very tense as one has to be super careful not to destroy the block behind/under it - and fighting is definitely a no around them. I wanted creative blocks so I could build mighty towers and castles... but when they all feel like paper mache it kinda spoils the fun. Without the ability to use the mouse wheel to pull up a copy of the block, it's a PITA to make repairs when damage occurs.

I know it is a pre-release, but I just wanted to bring it to your attention that it's quite simply not generating the config for me at all. Re-installed a few times too, but it just won't generate it.

Just a reminder to myself

You could add a tab to the survival inventory which loads all the blocks from the config and acts like the "blocks" tab in creative mode.

From /u/oltronix on reddit

I was thinking about something similar to the carpenters block, but instead of putting a material into a placed carpenters block, you would select the appearance of the block by using it on any block in the world. The block would then be placeable as you described. This would allow use of things like diamond blocks without affecting game balance.

From /u/BBolt on reddit

Maybe a combination of the two ideas would be the best. A block which can take on the texture of any block, and doesn't get used up when you place it. I wouldn't even mind if the recipe for such a block was a little expensive.

Extra Utilities' builders wand uses up creative blocks (decreases the stacksize). Will probably need to ASM the builders wand code or something.

I'm not sure if this already works. I'm doing something wrong then, I've tried using the wildcard, example: "ForgeMicroblock:microblock:*" but nothing changes. Forge Multipart or Microblocks uses nbt data to store what material it is so might be that you aren't supporting nbt yet? I don't know, would be cool to see in a future update if it's possible.

Not sure the best way to go about the harvestability part, but it'd be nice to have.

From reddit:

/u/topherkeey:

This is a great idea! Is is possible to add the functionality of middle-clicking to give yourself one of the selected, whitelisted block? This is an important feature of creative mode and is used in every build I've done in creative.

/u/squeek502:

That'd create a loophole that'd allow getting infinite of the whitelisted blocks. Can't think of a way to add that feature while avoiding that loophole.

/u/DoctorDeranged:

Is it possible to make it a type of ghost block? So if you open your inventory or a gui it would disappear, similar to the block glitch?

/u/squeek502:

Was just thinking about that. I could add an item that places its 'stored' block when used, and then middle click could 'store' the targeted block.

It'd be like a middle-ground between the mod's current implementation and this idea for a universally disguisable block (#1).