-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
Chunks don't load #8
Comments
same problem |
:/ |
I am going to test it as soon as I have the time, I am using iris on production and I don't have any issues my server is on 1.19.2 paper and I am using iris 2.3.13-1.19.3-hotfix |
I hope the bug will be fixed! |
This is an interesting issue while testing... it was very random There is an issue, but where... also not a related bug. Some mm mobs are spawning wrong 😕 I need to do more testing to figure out the issue, maybe turning on debug on both plugins would yield something 🤞🏻 |
debug gives more info about the plugin and what's happening it doesn't solve the bug, it helps identify the issue |
I tried with Here is the code snippet I used in the iris pack: {
"name": "Empty",
"derivative": "THE_VOID",
"vanillaDerivative": "THE_VOID",
"layers": [
{
"palette": [
{
"block": "iasurvival:modern_stone",
"weight": 200
},
{
"block": "minecraft:white_concrete",
"weight": 50
}
]
}
],
"generators": [
{
"generator": "empty",
"min": -40,
"max": 60
}
]
} |
@NextdoorPsycho you got any ideas why this whloud happen? |
I do also have the issue, hope it gets fixed soon :( |
Will be tested again, probably compatibility broke with some latest Iris update. |
I also need a full server log. |
Where do I send you this? The config was fresh installed tho so I guess you can just start with new config. Will send mclogs in something like 4hours |
Can you elaborate on this? Do you mean that if you use another pregeneration tool such as Chunky it happens, or if you are generating chunks live (i.e. no pregeneration happens at all)? |
Basically you're telling me that the default Iris configurations (with no custom block from itemsadder added) is not loading correctly when itemsadder-blocks-injector is installed? |
Oh no I meant that the default config with a custom block on the overworld.json and iablockinjector don't load so basically you can just add a custom block to the iris config and I guess you'll get the same issue |
What do you mean? @T1Doggo |
@CocoTheOwner I can't reproduce the issue perfectly, each time, it's random. also, @RePixelatedMC on discord told me that
@LoneDev6 the issue is, from what I understood, they are adding a custom block and the generation stops working From my testing, the generation works as usual, I also always pregen the world to 100K so I don't have any loading issues whiteout and when adding custom block's the generation is slow when using a 6GB server my testing server is 20GB RAM and I7 8th generation |
I mean the world do not load, i'm stuck in the loading screen while tping to the world. here's the full server logs tested on Purpur-1.19.2-1858, with Iris-2.3.9-1.19.2, ItemsAdder_3.3.1 and itemsadder-blocks-injector_0.0.7 |
@T1Doggo I recommend 8 GB ram and a CPU from 2013+... |
I have same problem with 20GB RAM |
No. I know what is happening with him. Basically if you have a world of Iris that was generated without custom block, and puts the custom blocks later, only chunks without custom block loads. But if you create the world with custom blocks, it doesn't load into vanilla minecraft or optifine (Fabric and forge works 100%, bug only happens on Vanilla and optifine) |
I'm so confused right now
We don't support fabric or forge with IA |
Fabric, forge and optifine client*** |
Test with this:
Result:
Result: |
Nice if it works with Fabric, but it would be great if it would also work with the normal Minecraft Vanilla |
It's useless work if you need to use a modded client to play in a specific server |
Already tried with fabric and sodium and still not working |
:/ |
anyway I think that the issue is from ItemsAdderBlockInjector, everything in iris is fine, same about iA |
I think so too |
Still getting this error when trying to pregen the world with iris, |
Try with 1.19 (not the .1 or .2) Fabric sodium |
first of all holy shit turn down your weight values. 1 concrete to 4 modern stone is the same thing and will yield you like 3000% more performance. |
and I'm not entirely sure what the problem is here. If I understand this correctly, you start your generation without custom blocks. Then you add custom blocks to your generation, and it breaks. Why not start with the custom blocks already added in the generation instead of shoehorning at it? There's a red label warning for force updating worlds for a reason or did I miss something, or do I not understand some thing about the situation? does this happen in the studio? |
you can't just throw ram at your problems to make them go away, I don't have this problem, nor can I replicate it, which is problematic for trying to figure out how to help |
if you use purpur we hook into a natively to optimize the chunk generation, anything else, and you're rolling the dice. for example, the reason we push for it so hard is that I have literally zero issues with things like this when I'm using purpur |
OK, after reading the entire thread, I am still very not understanding the problem. I understand that it has something to do with chunks not loading. Can someone please explain to me in English how they are causing and replicating the issue because I am very sick right now, and I'm just having a hard time following. Thanks. Feel free to message me on discord |
Not my problem. This is not our problem and is literally a game bug. Update = fix. Simple as that. They made 1.19.3 for a reason use it. And according to @Rakise its only with 1.19.2 |
Same, and there is a lot of spam going on here. To the reportersPlease post a proper Iris folder that I can drag and drop into my plugins folder so that I can test the issue. And please stop messaging with biased and unprecise information. Thanks. |
@LoneDev6 , BlockInjector supports 1.19.3? I cannot start plugin on Paper 1.19.3. |
Open a separate issue report then, and provide a proper server log of when the issue occurred. |
I'll try to explain it as simply as possible. If you create a world using Iris with custom blocks created by itemsadder (you can open the world in the studio as well), the world will not load in vanilla. But the world exists. How it works? Vanilla stays on the "generating terrain" screen but the client works 100% It plays sounds, it works packets that the player sends to the server and also takes damage, it is 100% functional, but the screen is stuck on that message "generating terrain". How do you prove that the world exists and is functional? Using Fabric. If you log in with a Fabric client, it loads the world with custom blocks created by itemsadder (I tested it on a paper, purpur, pufferfish, mirai server. All in 1.19.2). Now there is another problem, if the chunk that the Vanilla player spawns, there is no custom block (literally 0 custom blocks) this chunk works normally and the Vanilla player can use it (spawn in it, interact and break it). But chunks with custom blocks are invisible and don't load only in vanilla clients |
I am asking the same thing over and over but no one seems to understand that I need what I asked in order to identify the issue. |
Here is a simple iris package I changed from irisdemension/emtpy, the only change I made was to specify the layers in When use this pack to create a new world, on the server side, everything generates fine, no errors or warnings are reported. World generate like this way: On the client side, at the forge/fabric client, you can also enter the world normally and everything works fine. However, in the vanilla client, when you enter the world, your window is frozen in the loading terrains page and never finishes. On the server side, all blocks are loaded normally. I think this may be a bug related to the client side, or as [NextdoorPsycho] said, a bug from minecraft. If there are more questions, please feel free to ask me. Thanks for working on it. |
It is a Minecraft bug. And as I have stated, just update the damn game. There's nothing either of us can do if it's a game bug. The last guy that mentioned this to me I told him to update and it worked fine, just do that be the latest version of the game for latest fixes. |
I'm not against updating but how about ItemsadderBlockInjector not working on 1.19.3 |
Dear reporters, @bowencraft @Rakise @T1Doggo @Kuzmaniac I would be grateful if you provided a complete Iris folder for testing purposes. This issue is too long about an issue that I can't reproduce, I have no problems on 1.19.3 EVERYTHING WORKS FOR ME Regarding the Minecraft bug, updating the latest version, 1.19.3, should resolve the issue.
This is how all the messages are going... we would all like to solve your issues, so please work together with @LoneDev6 @NextdoorPsycho |
Here is a complete iris folder, used I believe the main arguments about this issue now is that using 1.19.3 would solve this problem. Nevertheless, ItemsAdderBlockInjector doesn't really support 1.19.3, so we can't actually use 1.19.3. I submitted a new issue on this subject: #9 |
I have the same problem with 1.19.3. The ItemsAdderBlocksInjector plugin (0.0.7) is not showing up when I do /pl, so I'm trying the 1.19.2
|
Here the server logs and ItemsAdder folder from a test server 1.19.2 |
You guys cant fix using bukkit api or NMS. The only fix i found is changing how the original jar works when register chunks. This issue needs to be closed. Update to 1.19.3 (client) since it's a 1.18-1.19.2 bug |
Thanks for the configuration @bowencraft https://streamable.com/j5j5w2 |
Hey!
whenever i add a custom block in the json files of iris the world doesn't load. sometimes it works but then only the chunk that contains the nine blocks doesn't load. with the standard iris files it works great but not with the new ones from ItemsAdder
Server on Paper 1.19.2
ItemsAdder_3.3.0b-r5
itemsadder-blocks-injector 0.0.7
Iris-2.3.13-1.19.3
The text was updated successfully, but these errors were encountered: