The official forums for this server are very dead. I'm calling out to those who run this server that visit this forum, looking for help.
Please bare in mind that I'm not a programmer, so if you respond please make note of this.
1.) Grass is not growing
2.) Super lag when someone is connecting to the server. It will lag until is says that user has joined.
3.) Large 512x512xETC maps take forever to decompress, and once it does, perl is using 1.8GB of memory. Eventually the server will shut down do to insufficient memory.
4.) How can I added timed messages at random from a list? (like cMss)
Thanks Leonardo... I'll try that channel. I was in #jtemods and #archives trying to find help but it's not very active either. I know mail is active so I'll give him a shout.
But still, if anyone on the forum has anything to say to help out I would greatly appreciate it. JTE is much more advanced than the rest, I just don't have the programming skills to fix it.
1. Perhaps JTE didn't add grass physics?
2. Yeah, JTE's server hangs while it's sending to a client
3. This is due to the fact that in Perl, there is no byte object, so all of the blocks are stored in lists which use probably 4-8 bytes per object
4. It's pretty easy, actually.
2 and 3 are perl's fault
4 is somewhatish easy, look in core.pl, copy one of the timers and replact it with a message displayer.
Actually, 2 could be fixed with some modification to either multithread the mapsending, or use MinerCPP's method. 3 is perl's fault though.
Even running a 256x256x256 map uses up ~800mb of memory lol oh well. If it's a perl limitation, not much can be done.
Quote from JoeyJo0 »
About the grass growing think
in the file with all the block info(blocks.pl? Can't remember) there should be the grass block somewhere.
Does it use 'grass_think'?
Might be disabled due to lag.
You're right, grass think was commented out. I haven't tested yet, going to wait for a new release of the server (if that ever happens) to do some testing.
JTE has announced a new server will be coded in C. Unknown if it will be made downloadable/purchasable or not.
Quote from JTE »
I'm programming a new server in C with extensive Lua scripting support. That's the news.
It should fix all of the current server's problems, particularly being threaded and efficient, and supporting way more things than my Perl script ever could. I was hoping someone else would have done something by now, but nothing has been shared with me. Since I'm on my own, I'll program my own.
The Archives has forgotten me. Their login message (which is still a cruddy text block instead of actually happening upon login) is overzealous about their relationship with World of Minecraft, ranting about how they're "the two greatest servers ever joined forces!1" and whatnot. Eh, I don't need it. Before BOTH there was me, and I'm still here, you'll see.
I don't know if I'll be selling this one too, or if I'll just run one giant server for everyone. I may well do just that. I have the resources.
As for the actual features? I'll list them later, when I open it to the public. I don't want to give away my plans this time, things that no other server has done. But there will definitely be multi-map support and many games and contests to participate in. The entire world automated, and nothing can go wrong. This is the Minecraft of the future. Collaboration is optional.
And when Notch takes Minecraft in a completely different direction, and when the client on the website becomes incompatible, and EVEN IF everyone sees the end of the great pirate server era...
in the file with all the block info(blocks.pl? Can't remember) there should be the grass block somewhere.
Does it use 'grass_think'?
Might be disabled due to lag.
You're right, grass think was commented out. I haven't tested yet, going to wait for a new release of the server (if that ever happens) to do some testing.
Yes, as it was commented out... there is no code in grass_think, so it wouldn't work anyways
Rollback Post to RevisionRollBack
Quote from NuclearDemon »
There are 10 kinds of people who understand binary.
Those who do.
And those that don't.
Quote from HeadHunter67 »
"I'd like to sssssssspeak to you about Jeeesssussssss...."
Quote from Theonlydoh2 »
Rain, rain, go away,
THAT'S WHAT ALL THE HATERS SAY.
Please bare in mind that I'm not a programmer, so if you respond please make note of this.
1.) Grass is not growing
2.) Super lag when someone is connecting to the server. It will lag until is says that user has joined.
3.) Large 512x512xETC maps take forever to decompress, and once it does, perl is using 1.8GB of memory. Eventually the server will shut down do to insufficient memory.
4.) How can I added timed messages at random from a list? (like cMss)
irc://irc.esper.net/minecraft/
But still, if anyone on the forum has anything to say to help out I would greatly appreciate it. JTE is much more advanced than the rest, I just don't have the programming skills to fix it.
2. Yeah, JTE's server hangs while it's sending to a client
3. This is due to the fact that in Perl, there is no byte object, so all of the blocks are stored in lists which use probably 4-8 bytes per object
4. It's pretty easy, actually.
[bookshelf] [bookshelf] [bookshelf] [bookshelf] [bookshelf] [bookshelf] [bookshelf] [bookshelf] [bookshelf] [bookshelf] [bookshelf] [bookshelf] [bookshelf] [bookshelf]
That is because nobody has come up with a way of making grass grow at random intevals perfectly
4 is somewhatish easy, look in core.pl, copy one of the timers and replact it with a message displayer.
Quality of output = Skill * Effort
in the file with all the block info(blocks.pl? Can't remember) there should be the grass block somewhere.
Does it use 'grass_think'?
Might be disabled due to lag.
Actually, 2 could be fixed with some modification to either multithread the mapsending, or use MinerCPP's method. 3 is perl's fault though.
[bookshelf] [bookshelf] [bookshelf] [bookshelf] [bookshelf] [bookshelf] [bookshelf] [bookshelf] [bookshelf] [bookshelf] [bookshelf] [bookshelf] [bookshelf] [bookshelf]
Even running a 256x256x256 map uses up ~800mb of memory lol oh well. If it's a perl limitation, not much can be done.
You're right, grass think was commented out. I haven't tested yet, going to wait for a new release of the server (if that ever happens) to do some testing.
http://forums.echidnatribe.org/index.ph ... opic=235.0
Yes, as it was commented out... there is no code in grass_think, so it wouldn't work anyways