Page 1 of 2

The schematics

PostPosted: 06 Jul 2013 08:21
by AnDwHaT5
Well everyone is making schems for the pokecentre and the common issue is that the blocks are to expensive. Not for nothing but why dont you guys put a security on the blocks when they spawn so people cant break them at all. It isnt that hard just change the block break time to -1 on generated pixelmon buildings. As you know -1 is pretty much bedrock or not breakable. That would get that out of the way and we wouldnt have to worry about the blocks (as much) i still dont rec the things that mr.m said not to put (iron blocks, diamond blocks, gold blocks.) An example is to use a function to identify the building and then put it as -1. I dont code in java i just get the idea of coding from CC's LUA which is the basic concept.

Re: The schematics

PostPosted: 06 Jul 2013 12:40
by GhostWolf2398
AnDwHaT5 wrote:It isnt that hard just change the block break time to -1 on generated pixelmon buildings.


I don't believe it is that simple, since the block break time is a property of the block type (all gold blocks have the same, etc), rather than a property of the individual block that is placed. Unless I'm mistaken.

Re: The schematics

PostPosted: 06 Jul 2013 18:05
by AnDwHaT5
No its like using a region like let me put it in lua because i am decent at that i dont know java.
If blocks == pixelmonBuilding then
blockBreak == -1
else
then what ever would be there. blocks is a function representing all spawned chuncks and pixelmonBuilding is a function that represents the spawned building. Then using the same coding or relevant to worldedit or guard it makes a region around the perimeter of the schem and then sets all blocks in that to the same block break event as bedrock.

Re: The schematics

PostPosted: 06 Jul 2013 21:28
by The_Nanobots
AnDwHaT5 wrote:If blocks == pixelmonBuilding then
blockBreak == -1
else
then what ever would be there.

I believe that would give you the error "bios:338: [string "<nameofprogram>"]:4: 'end' expected (to close 'if' at line 1)" It would not be as simple as you suggest (not that I know how it would be accomplished) I believe ars magica has a block that does this called the "Tower Protector" http://arsmagica.shoutwiki.com/wiki/Tower_Protector I'm not sure it would actually be worth it to add this becouse we just got 17 new colored blocks to use in 1.6.1. Do we need to add this just to use those overrated storage blocks? We could very easily just add new blocks to make these structures with.

Re: The schematics

PostPosted: 07 Jul 2013 07:13
by AnDwHaT5
That is a example of 2 functions that have been written that obviously has not been shown being used in conjunction. And as per end i dont see a reason to add it what will that accomplish if i added it. Its not like they are doing the mod in lua.

Re: The schematics

PostPosted: 07 Jul 2013 17:06
by MrMasochism
It's not possible to change the breakable properties of certain blocks in pixelmon buildings without affecting every other block of that type on the map

Re: The schematics

PostPosted: 07 Jul 2013 20:31
by AnDwHaT5
Really it isnt. I would think it is if the building gen that you have is in a function because if it is then you can modify the function to where ever it spawns.

Re: The schematics

PostPosted: 07 Jul 2013 21:44
by MrMasochism
It's really not possible. Each block is run from a single instance of a class, changing it in one place changes it everywhere

Re: The schematics

PostPosted: 08 Jul 2013 08:01
by AnDwHaT5
Ahh i get it so in order to do what i am suggesting they must have different block id's then everything in the world. Then how about you save each blocks texture then put them in a spot in the pixelmon folder in the mods assign them special ids then do that. Also make them only spawn able by gm. That would fix the issue its like a mod in a mod but easyer :P.

Re: The schematics

PostPosted: 08 Jul 2013 09:46
by gamingnut2
it probably not a big enough project that they would go out of there way to do that, plus people will probably wanna move into it and eventually expand.