mojira.dev

CocoaMix

Assigned

No issues.

Reported

Comments

confirmed without resourcepack

On Fri, Nov 21, 2014 at 6:18 PM, Lucas Ignacio Morrison Osorio (JIRA) <
bugs@mojang.com> wrote:

> Lucas Ignacio Morrison Osorio
> <https://bugs.mojang.com/secure/ViewProfile.jspa?name=ToonLucas22>
> commented on an issue Re: Lightning Render Issue
> <https://bugs.mojang.com/browse/MC-74545>
>
> May be an issue with your resource pack. Please change it to the default
> resource pack and check the issue there.
> [image: Add Comment]
> <https://bugs.mojang.com/browse/MC-74545#add-comment> Add Comment
> <https://bugs.mojang.com/browse/MC-74545#add-comment>
> Minecraft <https://bugs.mojang.com/browse/MC> / [image: Bug]
> <https://bugs.mojang.com/browse/MC-74545> MC-74545
> <https://bugs.mojang.com/browse/MC-74545> Lightning Render Issue
> <https://bugs.mojang.com/browse/MC-74545>
> Slimeblocks do not render behind Lightning
> This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) [image:
> Atlassian logo]
>

players in creative mode should not be able to die unless killed by /kill.
Please actually fix before closing it

On Sun, Nov 16, 2014 at 1:49 AM, [Mod] Kumasasa (JIRA) <bugs@mojang.com>
wrote:

> [Mod] Kumasasa
> <https://bugs.mojang.com/secure/ViewProfile.jspa?name=kumasasa> resolved
> an issue as Duplicate
>
> Amplifiers beyond 4 are not supported.
> Minecraft <https://bugs.mojang.com/browse/MC> / [image: Bug]
> <https://bugs.mojang.com/browse/MC-74368> MC-74368
> <https://bugs.mojang.com/browse/MC-74368> High Amplified Healing
> Potions can kill Players in Creative
> <https://bugs.mojang.com/browse/MC-74368> Change By: [Mod] Kumasasa
> <https://bugs.mojang.com/secure/ViewProfile.jspa?name=kumasasa>
> Resolution: Duplicate Status: Open Resolved [image: Add
> Comment] <https://bugs.mojang.com/browse/MC-74368#add-comment> Add
> Comment <https://bugs.mojang.com/browse/MC-74368#add-comment>
> This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) [image:
> Atlassian logo]
>

Update: Any mob crashes the game when a fishing hook is thrown at them while this specific clock is running

I delcare this issue not resolved. Since the symbol CAN still be inserted into command blocks, the functionality should still be in the game. If you truly wish to resolve this issue, I highly suggest making it work again, or removing the ability and functionality of the symbol

Can confirm for 1.8.3

oops, how do i delete a ticket. I goofed. I was missing a single letter. I'm sorry for this mistake

Can confirm as well in my tests

After a bit more experimenting, I found this most commonly happens when the repeater is locked by a "subtraction mode" comparator

Can confirm for 1.8 pre-release

You guys aren't understanding!! I know that a witherskull will appear for a short time when summoned.... but this bug causes the witherskull to randomly appear while it's floating. It could be 1 second, 4 seconds, 10 second intervals between flashing. It's not just when summoned, it happens while it's just floating there

this has been in the game for a while. This is a type of advanced BUD switch. The regular pistons you have on the bottom have a block of air above them, then a redstone block. The redstone block is actually preparing the bottom piston for a BUD. When you place the redwire or torch even one block away from the piston (like air block in between), it activated the BUD switch. This type is not very commonly seen, but can happen in certain situations

I can confirm the exact same thing. It's extremely annoying.
https://imgflip.com/gif/9sj0x

nvm, I have resolved this. I have a mass amount of entities and when I press tab, the game creates a list of all the entity ids in the chat, which lags the game for a few minutes.

I have figured out the problem. In this map, it spawns huts and buildings with torches inside. It then randomly deletes some of the buildings, but for some reason, the lighting from the torch stays. Please fix

update The skeleton actually never fires when freshly summoned or naturally spawned in.

can confirm problem still for 14w21b

Load more comments