Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom structuretypes failing to load #22

Open
loopyluke opened this issue Oct 18, 2011 · 5 comments
Open

Custom structuretypes failing to load #22

loopyluke opened this issue Oct 18, 2011 · 5 comments

Comments

@loopyluke
Copy link

So I've edited the structuretypes.yml file to customize the default shape and blocks to be used in a standard memorystone like this:

-   structure:
    -   z: 1
        material: OBSIDIAN
        y: 1
        x: 1
    -   z: 1
        material: GLOWSTONE
        y: 3
        x: 1
    -   z: 1
        material: BEDROCK
        y: 0
        x: 1
    -   z: 1
        material: OBSIDIAN
        y: 2
        x: 1
    rotator: NONE
    name: Memory Stone
    metadata:
        distanceLimit: '0'
        memorizecost: '200'
        teleportcost: '50'
        global: 'false'
        buildcost: '1000'
        type: MEMORYSTONE
        permissionRequired: memorystone.create.local

The structure works fine and memorystones are created, which function normally.

However upon reloading the server the existing stones do not load and I receive these errors:

19:26:59 [INFO] [MemoryStone] loaded 1 structure types
19:26:59 [WARNING] [MemoryStone] New: structure was bad
19:26:59 [WARNING] [MemoryStone] A structure couldn't be loaded
19:26:59 [INFO] [MemoryStone] Loaded 0 structure(s)

Upon reverting the structuretypes.yml to default it works fine and reloads the structures on server reload.

@CmdrDats
Copy link
Owner

I can't quite make out the shape of the stone you're creating here, but I have noticed there are problems if you don't have a corner stone, ie, you need stones at the bottom corners (hence the sqaure shape). I should probably rework it to use the block behind the sign as the base stone instead..

On Tuesday 18 October 2011 at 11:09 AM, loopyluke wrote:

So I've edited the structuretypes.yml file to customize the default shape and blocks to be used in a standard memorystone like this:

  • structure:
  • z: 1
    material: OBSIDIAN
    y: 1
    x: 1
  • z: 1
    material: GLOWSTONE
    y: 3
    x: 1
  • z: 1
    material: BEDROCK
    y: 0
    x: 1
  • z: 1
    material: OBSIDIAN
    y: 2
    x: 1
    rotator: NONE
    name: Memory Stone
    metadata:
    distanceLimit: '0'
    memorizecost: '200'
    teleportcost: '50'
    global: 'false'
    buildcost: '1000'
    type: MEMORYSTONE
    permissionRequired: memorystone.create.local

The structure works fine and memorystones are created, which function normally.

However upon reloading the server the existing stones do not load and I receive these errors:

19:26:59 [INFO] [MemoryStone] loaded 1 structure types
19:26:59 [WARNING] [MemoryStone] New: structure was bad
19:26:59 [WARNING] [MemoryStone] A structure couldn't be loaded
19:26:59 [INFO] [MemoryStone] Loaded 0 structure(s)

Upon reverting the structuretypes.yml to default it works fine and reloads the structures on server reload.

Reply to this email directly or view it on GitHub:
#22

@ryantheleach
Copy link
Contributor

If thats the bug making all the x's and z's 0 should help its supposed to be a vertical pillar of.

glowstone
obsidian
obsidian
bedrock

@loopyluke
Copy link
Author

We discussed this and figured out that this was our problem, not sure how it slipped past both of us so easily!

@loopyluke loopyluke reopened this Oct 18, 2011
@ryantheleach
Copy link
Contributor

got loopy to reopen as I believed it should still work even like this.
Loopy is a co-admin of my server, I had no clue on this bug so told him to palm it off to github.

@CmdrDats
Copy link
Owner

hehe, cool - you're right, this is an issue that should be fixed up

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants