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

Bug: Suspicious Page not generating as normal #353

Open
samuelask opened this issue Nov 14, 2024 · 7 comments
Open

Bug: Suspicious Page not generating as normal #353

samuelask opened this issue Nov 14, 2024 · 7 comments
Assignees

Comments

@samuelask
Copy link

samuelask commented Nov 14, 2024

The suspicious page is only generating a blank page in the end loottable location.

To Reproduce
Steps to reproduce the behavior:

  1. Go to the end and look for end cities
  2. Find a end city, open up the loot chest
  3. You will see that every Suspicious page is empty, just a blank page. However the Uni dialer is spawning as normal.

Expected behavior
Your supposed to find a suspicious page and it will automatically change its nbt data to display a non generated adress. Making it so you can explore other dimensions.

Screenshots
End city loot
2024-11-14_17 12 02

Mod version
JSG 1.12.2
Version 4.11.2.8

Additional context
Im playing with galacticraft + its extended mod. I have 45 different dimensions that all have non generated gates. It should 100% generate a Suspicious page with a non generated adress. (And it does when manually spawning in structures containing Suspicious pages)

My whole JSG config (as .zip)
jsg.zip

@Fredyman95
Copy link
Collaborator

I think that suspicious page should generates only in JSG structures + in stronghold (this page generate only END gate address)

but maybe we messed something up...

@samuelask
Copy link
Author

samuelask commented Nov 14, 2024

I think that suspicious page should generates only in JSG structures + in stronghold (this page generate only END gate address)

but maybe we messed something up...

“end_city_treasure.json” has the “jsg:page_notebook“ in it. So should be intended to spawn a suspicious page?

Maybe “spawnSusPageInChest” isn’t called when dealing with other loottables other than jsg? It’s supposed to replace the “jsg:page_notebook“ in the chest to a Suspicious page

@Fredyman95
Copy link
Collaborator

“end_city_treasure.json” has the “jsg:page_notebook“ in it. So should be intended to spawn a suspicious page?

Maybe “ spawnSusPageInChest” isn’t working properly. It’s supposed to replace the “jsg:page_notebook“ in the chest to a Suspicious page

page_notebook have more states [data] - empty, filled, suspicious ...

so there is no give command for suspicious as /give @p suspicious_page 1 0 but if I remember right its /give @p notebook_page 1 2

@samuelask
Copy link
Author

samuelask commented Nov 14, 2024

“end_city_treasure.json” has the “jsg:page_notebook“ in it. So should be intended to spawn a suspicious page?
Maybe “ spawnSusPageInChest” isn’t working properly. It’s supposed to replace the “jsg:page_notebook“ in the chest to a Suspicious page

page_notebook have more states [data] - empty, filled, suspicious ...

so there is no give command for suspicious as /give @p suspicious_page 1 0 but if I remember right its /give @p notebook_page 1 2

Yeah but what would be the point in spawning in an empty page as end loot? I think it’s supposed to spawn a suspicious one.

@samuelask
Copy link
Author

samuelask commented Nov 14, 2024

Maybe the loottable is named wrong here?

case "loot_end": should be “end_city_treasure”

@Fredyman95
Copy link
Collaborator

Maybe the loottable is named wrong here?

case "loot_end": should be “end_city_treasure”

If this will be wrong there will will be no loot at all.

I'm still leaning towards it like this: #353 (comment)

@samuelask
Copy link
Author

samuelask commented Nov 14, 2024

Loot would still spawn I think, the end_city_treasure.json would make sure of it.

Also there is no reference to a “loot_end“ anywhere. So that case is literally doing nothing anyway.

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

No branches or pull requests

3 participants