Very often on the map there are " phantom blocks" . Areas such units are enormous , when you try to move to the area player throws after rejoining the server problem is solved . But not for long. How to solve this problem ?

The problem is seen in the version of RTG-1.7.10-0.8.0-snapshot- 5 , but it is very unobtrusive , on versions of the above problem is critical

KCouldron 1.7.10 1614 201 (checked on Thermos 56)

@DrLeonardo We don't officially support KCauldron, so there''s not much we can do to help. The only way we could help is if you could reproduce this issue using only a Forge server.

The one thing I could suggest is to try using the latest 1.0 snapshot to see if it fixes the problem. Just be sure to backup your world because upgrading from 0.8-snapshot-5 might create some chunk walls.

I'm closing this issue, but I'll re-open if it turns out to be reproducible using only Forge.

I haven't noticed a single instance of anything like this, nor has anyone else reported anything like this. I assume this is a KCauldron issue.

Tests have shown that the core server is not guilty .
Now there is a bug in the Thermos

The problem is seen in the version of RTG-1.7.10-0.8.0-snapshot- 5 , but it is very unobtrusive , on versions of the above problem is critical

@whichonespink44 I can confirm this. I using 1.0-snapshot 2 will happend when I only use Forge in single game. Also KCauldron had this problem too.
And now 90% of Mod servers are using KCauldron or Thermos, you said do not support KCauldron, I think this is not a wise choice.

@sourcepowered I agree , do support KCauldron and Thermos

So this is happening with just Forge and RTG installed? If so, please provide a seed so we can investigate further.

@whichonespink44 OK, sir. I will try to reproduce the problem.

@whichonespink44
I find the problem. Please see:
Used in Forge Client, single game, verson 1.7.10-1.0.1.

And you can see this area is extremely unusual.

And I also tried to use the KCauldron and Thermos, it's still not normal.
The log file is very normal, no any warning or error.

And, you can see that problem is a regular distribution (Looks like a rectangle):

Please post the entire log file (fml-client-latest.log) and I'll try to reproduce the problem.

@whichonespink44 The trees does not seem to be some ghost blocks ... But the shrub still has the problem. And I will send you the world archive and log file, please wait.
You can see this, it's not normal I think (I will send you this archive):

The coordinates are: -213, 51.

It seems that RTG is very supportive of KCauldron and Thermos, which should be Mod's own BUG.

@whichonespink44
The world archive: https://mega.nz/#!MUBWmRqb!KgBcDI3CeB96dyPg48ZX3QZBXAbFwmgIyRusPSsUqac

The log file (It's too big, I can't upload it to pastebin.com): https://mega.nz/#!QVQGXTDZ!RESLLQMlL8F5bJy5rWHUnOdOdP5jCG9fLoIgx_YuRFE

Ok, thanks for that stuff.

We'll take a look in a couple hours and see if we can figure out what's going on.

@whichonespink44
What the ... Please see this:

Is still just archive I send you, and the coordinates are -241, 220.
I only once again load the world ..........

@whichonespink44
After the actual test, if I am in the client to generate a world, then I'll copy the world to the server, will also produce the above problems: The world chasm ?!

Even modifying the "level-tyle" to "RTG" is invalid.

And, RTG does not seem to support the mutil world:
First, generate a normal world.
Second, use the Multiverse plugin to import a already exists RTG world.
Third, the world chasm???!!! Almost as above.

This has nothing to do with KCauldron or Thermos, it should be the problem of Mod itself I think.
So I wonder if it's the second time loading the map that will lead to the problem.

**I'm sorry I said so much, but now there are 3 problems:

1. Ghost blocks.
2. The world chasm?!
3. Can not support Mutil world (even modify the level-type).**

Can not support Mutil world (even modify the level-type).

RTG doesn't work outside of Dim 0.

@srs-bsns @whichonespink44

RTG doesn't work outside of Dim 0.

But RWG, BOP and other Mods are supported.
I don't think we should maverick, support the Thermos and KCauldron not a difficult thing. And the number of 1.7.10 users currently still more and more ( I think many people don't like Microsoft, 1.8, you know ) and Thermos and KCauldron is the best server side. BOP said no longer support 1.7.10, and finally they are updated because too many users using 1.7.10.
We need your help. If you do not support, we can only use the old version (such as RWG) of mod, if there is a BUG or a lot of bugs, we can not fix it, because we are not a programmer. We can only let the server go to worse.
Please help 1.7.10 users, like me, like him. Thank you very much, as well as a server creator.

if you are still using 1.7.10, i know the solution to your problem.
start stopping.

yes, everything else is kinda in flux right now, but modders are settling down on 1.9.4 currently, and we too will soon have a usable version out.

its impossible for us to keep maintaining a mod for a version of minecraft that is approaching an age of 3 years, while staying up to date with the newest versions at the same time, let alone fix some weird bug in an api that we do not support.

No one should be starting new servers in 1.7.10 now anyway, and if you are using kcauldron and have these issues, you probably have already stopped using rtg, as the incompatibility looks pretty severe.

@sourcepowered The log file that you provided is showing that you have a lot of other mods installed in addition to RTG. Please try reproducing this issue with just Forge and RTG installed. And be sure to provide a world seed so we can investigate further. In the meantime, I'm going to close this issue again, as it's almost certainly nothing to do with RTG.

@topisani
Yes, sir, you are right, but there are some big problems:
If quit using Bukkit, choose what server software and it must have PLUGINS function?
Is it really only use mojang's server software with forge?
You know, if there is no plugins, you can not protect the server, to achieve more functionality, such as login(like AuthMe), and Plots(like PlotSquared) and some plugins like WordGuard and more and more.
And if there is no plug-in, how anti-cheat? Disable some items(You know some of the items are dangerous, can destroy the server and players' efforts)?
There are many problems simply can not be expressed in words. There are many excellent Mod such as IC2, TF, but they only support 1.7.10, either. (1.8 and 1.9 has Sponge, it's great but it only support 1.8+).
And if using 1.7.10, you can only choose KCauldron or Thermos...............
So, would you please tell me how should I do? Give up all this?
It is obvious that all this is a contradiction.
Sir, I think we must support it, although I am a Spigot user. Sponge in the efficiency and ease of use, compared with Thermos, HUGE DIFFERENCE. we can not compared them, Sponge is too weak, simply not worth mentioning. And Sponge lack of too many important plug-ins. Now most Mod servers are using Thermos.
The stakes we must know.

@AuthMe You're free to use whatever you want... but we're also free to support (or in this case, not support) whatever we want. And currently, the only server platform we support is Forge.

The reason we only support Forge isn't because we don't like Bukkit or Spigot.... it's because we're a small team with a lot of tasks to do. We just don't have the time to support multiple server platforms at the moment, sorry.

If you absolutely must have realistic terrain, you'll either have to find another mod that does it, or fork RTG and add support yourself.

@AuthMe

1. sponge is the plugin system we have chosen to support, because it is very unobtrusive and generally avoids problems like this - no, its not yet perfect, but evidentally, neither are the things discussed here.
2. Otherwise, forge alone could be considered - there are mods like FTB-Utils which allow for land claiming and such, but yes, i am aware these things are all way better supported in actual plugin systems.

Other than that, as pink already said, we simply cant support every obscure plugin api out there especially not for a version as old as 1.7.10, and especially not now, two weeks after we have released the final major version for 1.7.10, but if any of you know java, you are free to fix it and send us a pull request.