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

All spawners in bo3's are pig spawners in builds 150+ (Spigot 1.10) #460

Closed
MCPitman opened this Issue Sep 17, 2016 · 4 comments

Comments

Projects
None yet
4 participants
@MCPitman

MCPitman commented Sep 17, 2016

Tested bo3s with various mob spawners, builds 150 and up place pig spawners only. Build 149 works fine (Spigot 1.10).

@BakermanLP

This comment has been minimized.

Show comment
Hide comment
@BakermanLP

BakermanLP Sep 27, 2016

This is, in my opinion, no problem with TerrainControl. I think, that is a new structure or new data in the nbt files. This seems to be a 1.10 change. The old nbt file contained:

? ''
: - EntityId: Zombie
  - MaxNearbyEntities: !short "6"
  - RequiredPlayerRange: !short "16"
  - SpawnCount: !short "4"
  - id: MobSpawner
  - MaxSpawnDelay: !short "800"
  - SpawnRange: !short "4"
  - Delay: !short "0"
  - MinSpawnDelay: !short "200"

The new nbt data contains the following:

? ''
: - MaxNearbyEntities: !short "6"
  - RequiredPlayerRange: !short "16"
  - SpawnCount: !short "4"
  - SpawnData:
    - id: Zombie
  - MaxSpawnDelay: !short "800"
  - Delay: !short "0"
  - SpawnRange: !short "4"
  - MinSpawnDelay: !short "200"
  - SpawnPotentials: !list_compound
    - - Entity:
        - id: Zombie
      - Weight: 1
  - id: MobSpawner

I git a demonstation nbt from ZoefyC on the mctcp forum. Here it is:

MobSpawner.zip

I am using TerrainControl Forge version build 158, Minecraft 1.10.2 and forge 2092.

Please try it out and comment here.

Michael (aka BakermanLP)

BakermanLP commented Sep 27, 2016

This is, in my opinion, no problem with TerrainControl. I think, that is a new structure or new data in the nbt files. This seems to be a 1.10 change. The old nbt file contained:

? ''
: - EntityId: Zombie
  - MaxNearbyEntities: !short "6"
  - RequiredPlayerRange: !short "16"
  - SpawnCount: !short "4"
  - id: MobSpawner
  - MaxSpawnDelay: !short "800"
  - SpawnRange: !short "4"
  - Delay: !short "0"
  - MinSpawnDelay: !short "200"

The new nbt data contains the following:

? ''
: - MaxNearbyEntities: !short "6"
  - RequiredPlayerRange: !short "16"
  - SpawnCount: !short "4"
  - SpawnData:
    - id: Zombie
  - MaxSpawnDelay: !short "800"
  - Delay: !short "0"
  - SpawnRange: !short "4"
  - MinSpawnDelay: !short "200"
  - SpawnPotentials: !list_compound
    - - Entity:
        - id: Zombie
      - Weight: 1
  - id: MobSpawner

I git a demonstation nbt from ZoefyC on the mctcp forum. Here it is:

MobSpawner.zip

I am using TerrainControl Forge version build 158, Minecraft 1.10.2 and forge 2092.

Please try it out and comment here.

Michael (aka BakermanLP)

@Mickket

This comment has been minimized.

Show comment
Hide comment
@Mickket

Mickket Sep 29, 2016

I tested the demonstration nbt with the latest build of spigot and terraincontrol-bukkit. Still getting pig spawners.

Mickket commented Sep 29, 2016

I tested the demonstration nbt with the latest build of spigot and terraincontrol-bukkit. Still getting pig spawners.

@BakermanLP

This comment has been minimized.

Show comment
Hide comment
@BakermanLP

BakermanLP Sep 30, 2016

Can you make a zip or anything of your terrain control config folder, where your WorldConfig.ini and all other stuff is included? I'll have a look at that.

BakermanLP commented Sep 30, 2016

Can you make a zip or anything of your terrain control config folder, where your WorldConfig.ini and all other stuff is included? I'll have a look at that.

@rutgerkok rutgerkok closed this in 6bdbdc1 Oct 1, 2016

@rutgerkok

This comment has been minimized.

Show comment
Hide comment
@rutgerkok

rutgerkok Oct 1, 2016

Contributor

With a bit of luck, build 162 should fix this.

Contributor

rutgerkok commented Oct 1, 2016

With a bit of luck, build 162 should fix this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment