<!-- 
RSS generated by JIRA (9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13) at Sun Jan 12 12:25:10 UTC 2025

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>Mojang Studios Jira</title>
    <link>https://bugs.mojang.com</link>
    <description>This file is an XML representation of an issue</description>
    <language>en</language>    <build-info>
        <version>9.12.2</version>
        <build-number>9120002</build-number>
        <build-date>10-01-2024</build-date>
    </build-info>


<item>
            <title>[MC-10679] Hopper Cool-Down is messed up</title>
                <link>https://bugs.mojang.com/browse/MC-10679</link>
                <project id="10400" key="MC">Minecraft: Java Edition</project>
                    <description>&lt;p&gt;As Dinnerbone tweeted, he changed the Hoppertimings in the latest Snapshot (&lt;a href=&quot;https://twitter.com/Dinnerbone/status/307446745594478592&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://twitter.com/Dinnerbone/status/307446745594478592&lt;/a&gt;).&lt;br/&gt;
After a short test I found out, that they now update every 9 gameticks (4.5 redstoneticks), instead of every 8 gameticks (4 redstoneticks), which makes it incredibly difficult to time hoppers.&lt;br/&gt;
For example if you want to get one item out of a hopper you now would have to depower it for exactly 4.5 redstoneticks wich is not really possible, or only possible with a pretty big circuit. You can&apos;t just depower it for 4 redstone because you would get 0 to 1 items and neither for 5, because you would get 1 to 2 items (It&apos;s unreliable).&lt;br/&gt;
Furthermore it doesn&apos;t make sense that a redstoneitem (like the hopper) updates every 4.5 ticks (wich is not an integer) instead of every 4 ticks (or another whole number)&lt;br/&gt;
After a look into the sourecode my assumption, that it&apos;s a bug got confirmed, because after every time, the hopper takes an item, it set&apos;s the cool-down to 8. The bug is that the algorithm checks if the cool-down is greater than zero. So eight ticks after the last update the cool-down will reach 0, but the hopper won&apos;t update until the next tick, wich makes it a total of 9 ticks in between 2 hopper updates instead of the wanted 8.&lt;/p&gt;</description>
                <environment></environment>
        <key id="24649">MC-10679</key>
            <summary>Hopper Cool-Down is messed up</summary>
                <type id="1" iconUrl="https://bugs.mojang.com/secure/viewavatar?size=xsmall&amp;avatarId=18903&amp;avatarType=issuetype">Bug</type>
                                    <status id="5" iconUrl="https://bugs.mojang.com/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="1">Fixed</resolution>
                                        <assignee username="dinnerbone">[Mojang] Nathan Adams</assignee>
                                    <reporter username="turbocube">Turbocube644</reporter>
                        <labels>
                            <label>hopper</label>
                            <label>redstone</label>
                    </labels>
                <created>Fri, 1 Mar 2013 21:59:32 +0100</created>
                <updated>Sun, 6 Sep 2015 22:47:50 +0200</updated>
                            <resolved>Mon, 4 Mar 2013 15:19:33 +0100</resolved>
                                    <version>Snapshot 13w09c</version>
                                    <fixVersion>Snapshot 13w10a</fixVersion>
                                                        <votes>4</votes>
                                    <watches>2</watches>
                                                                            <comments>
                            <comment id="49247" author="lexxaman" created="Sun, 3 Mar 2013 02:54:42 +0100"  >&lt;p&gt;This is very important, IMO. I had a machine that halved (rounding down) the amount of a specific item put in into points. And it did so as fast as the hoppers could send out items. So input 64 coal in the coal specific machine and get 32 points to your specific scoreboard, yet now, the more realistic situation is: Put in 64 coal and get 36 points. This is highly concerning. It  uses a clock that repeats every 8 Redstone Ticks (16 In-Game) which was perfect for the duration of a hopper sending out 2 items, but now, with a need for 9 (18), an odd number of Redstone ticks, it is rendered useless and not fixable within the space provided. I have tried decreasing the clock by a tick (which is doubled by the clock) which results in 28 points being given. This proved the need for an additional redstone tick (which is the result of two half ticks). So, not to drone on anymore, I believe this is an important issue to fix in the future.&lt;/p&gt;</comment>
                            <comment id="48854" author="kumasasa" created="Fri, 1 Mar 2013 23:10:35 +0100"  >&lt;p&gt;Please do not mark unreleased versions as affected. You do not have access to this yet.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                        <customfield id="customfield_10500" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Confirmation Status</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10300"><![CDATA[Unconfirmed]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_11700" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_11600" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i0k2z3:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                    </customfields>
    </item>
</channel>
</rss>