Jump to content

Recommended Posts

Posted

I have a tile entity that gets the world time. The method description says that this time wraps from 23999 to 0 and the then counts back to 23999. However that is not what I find when I try to use it. When I print it to consol the world time is additive past 23999 it seems forever.Any ideas why the time doesnt wrap?

 

My Tile Entities updateEntity method

 

 

 

@Override
public void updateEntity() {

	long time = this.worldObj.getWorldInfo().getWorldTime();//gets the world time of day
        System.out.println("world time is " + time);
       
	if ((time == 1 || time == 8001 || time == 16001) && !worldObj.isRemote){ //gets specific world time
		//DO STUFF HERE
	}

}

 

 

 

in the //DO STUFF HERE section the stuff I do stops happening cause of the world time issue where the time doesnt wrap.

[Edit] I solved the previous stuff that was posted below this it was a stupid error on my part

 

Posted

I solved the issue by doing

 

if (time >=24000){

  this.worldObj.getWorldInfo().setWorldTime(0);

  }

but it is still weird why it wont wrap on its own like the method description says it should

Posted

You shouldn't be manipulating world values. This value (worldTime) is not actually used much in vanilla, but still someone might be using it in mod.

Simply do: time % 24000L, don't set it.

 

And btw.:

it is still weird why it wont wrap on its own like the method description says it should

What description? (There is nothing that says it should) :D

1.7.10 is no longer supported by forge, you are on your own.

Posted

Yeah, don't screw with that value.

 

I'm actually using it right now and I expect it to go above 23999 in order to provide seasonal shifts.

Apparently I'm a complete and utter jerk and come to this forum just like to make fun of people, be confrontational, and make your personal life miserable.  If you think this is the case, JUST REPORT ME.  Otherwise you're just going to get reported when you reply to my posts and point it out, because odds are, I was trying to be nice.

 

Exception: If you do not understand Java, I WILL NOT HELP YOU and your thread will get locked.

 

DO NOT PM ME WITH PROBLEMS. No help will be given.

Posted

The Comment above the getWorldTime() method says

 **
     * Get current world time
     */
    public long getWorldTime()
    {
        return this.worldTime;
    }

"

 

and the comment above the worldTime says

/** The current world time in ticks, ranging from 0 to 23999. */
    private long worldTime;

 

which is why I expected it to wrap from 23999 back to 0

Posted

That may have been true once, but if you look at

    /**
     * Set current world time
     */
    public void setWorldTime(long p_76068_1_)
    {
        this.worldTime = p_76068_1_;
    }

in the same class, you'd notice that it doesn't enforce the note in the javadoc (which was written by someone contributing to MCP, not Mojang).

 

And if you trace all usages back around to the things that actually make it go up, you'll notice a continuous lack of any %24000 math, except here in WorldServer.java:

 

public void tick() {
        //...
        if (this.areAllPlayersAsleep()) {
            if (this.getGameRules().getGameRuleBooleanValue("doDaylightCycle")) {
                long i = this.worldInfo.getWorldTime() + 24000L;
                this.worldInfo.setWorldTime(i - i % 24000L);
            }
            this.wakeAllPlayers();
        }
        //...
}

 

Which goes out of its way to insure that the value isn't truncated to 23999.

Apparently I'm a complete and utter jerk and come to this forum just like to make fun of people, be confrontational, and make your personal life miserable.  If you think this is the case, JUST REPORT ME.  Otherwise you're just going to get reported when you reply to my posts and point it out, because odds are, I was trying to be nice.

 

Exception: If you do not understand Java, I WILL NOT HELP YOU and your thread will get locked.

 

DO NOT PM ME WITH PROBLEMS. No help will be given.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Announcements



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • When I first heard about Bitcoin back in 2018, I was skeptical. The idea of a decentralized, digital currency seemed too good to be true. But I was intrigued as I learned more about the technology behind it and its potential. I started small, investing just a few hundred dollars, dipping my toes into the cryptocurrency waters. At first, it was exhilarating to watch the value of my investment grow exponentially. I felt like I was part of the future, an early adopter of this revolutionary new asset. But that euphoria was short-lived. One day, I logged into my digital wallet only to find it empty - my Bitcoin had vanished without a trace. It turned out that the online exchange I had trusted had been hacked, and my funds were stolen. I was devastated, both financially and emotionally. All the potential I had seen in Bitcoin was tainted by the harsh reality that with decentralization came a lack of regulation and oversight. My hard-earned money was gone, lost to the ether of the digital world. This experience taught me a painful lesson about the price of trust in the uncharted territory of cryptocurrency. While the technology holds incredible promise, the risks can be catastrophic if you don't approach it with extreme caution. My Bitcoin investment gamble had failed, and I was left to pick up the pieces, wiser but poorer for having placed my faith in the wrong hands. My sincere appreciation goes to MUYERN TRUST HACKER. You are my hero in recovering my lost funds. Send a direct m a i l ( muyerntrusted ( @ ) mail-me ( . )c o m ) or message on whats app : + 1 ( 4-4-0 ) ( 3 -3 -5 ) ( 0-2-0-5 )
    • You could try posting a log (if there is no log at all, it may be the launcher you are using, the FAQ may have info on how to enable the log) as described in the FAQ, however this will probably need to be reported to/remedied by the mod author.
    • So me and a couple of friends are playing with a shitpost mod pack and one of the mods in the pack is corail tombstone and for some reason there is a problem with it, where on death to fire the player will get kicked out of the server and the tombstone will not spawn basically deleting an entire inventory, it doesn't matter what type of fire it is, whether it's from vanilla fire/lava, or from modded fire like ice&fire/lycanites and it's common enough to where everyone on the server has experienced at least once or twice and it doesn't give any crash log. a solution to this would be much appreciated thank you!
    • It is 1.12.2 - I have no idea if there is a 1.12 pack
  • Topics

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.