Improved malfunction sound

[vistaero]

No description provided.

[eccentricdevotion]

The only ones I actually like are tardis_hum_10, tardis_hum_11, and tardis_malfunction. The others I don't think are an improvement on the original SFX (maybe only in the quality of the sound...)

[eccentricdevotion]

The hum sounds are deliberately one object, so that one is chosen at random...

[vistaero]

The problem with all hums in one object is that you can't place the Stream property, and set it to true, so currently the game freezes (every 5000 ticks) while it's loading the audio file which is going to play.

I think it's worth to make the randomizer server-side if we get ride of those freezings. Or even instead of a randomizer, a player preference, so we can choose a specific hum for our TARDISes.

[eccentricdevotion]

What's wrong with:

"tardis_hum": {
        "category": "ambient",
        "sounds": [
            {
            "name": "tardis_hum",
            "stream": true
            },
            "tardis_hum_1",
            "tardis_hum_2",
            "tardis_hum_3",
            "tardis_hum_4",
            "tardis_hum_5",
            "tardis_hum_6",
            "tardis_hum_7",
            "tardis_hum_8",
            "tardis_hum_9",
            "tardis_hum_10",
            "tardis_hum_11"
        ]
    },

[vistaero]

Oh, I didn't know that. I couldn't find an example of multiple sound files with the stream property. But, I still think that a player preference to choose the hum would be a right decision.

[eccentricdevotion]

I always think the work should be done by the client wherever possible, maybe:

    "tardis_hum": {
        "category": "ambient",
        "sounds": [
            {
            "name": "tardis_hum_1",
            "type": "event"
            },
            {
            "name": "tardis_hum_2",
            "type": "event"
            },
            {
            "name": "tardis_hum_3",
            "type": "event"
            },
            {
            "name": "tardis_hum_4",
            "type": "event"
            },
            {
            "name": "tardis_hum_5",
            "type": "event"
            },
            {
            "name": "tardis_hum_6",
            "type": "event"
            },
            {
            "name": "tardis_hum_7",
            "type": "event"
            },
            {
            "name": "tardis_hum_8",
            "type": "event"
            },
            {
            "name": "tardis_hum_9",
            "type": "event"
            },
            {
            "name": "tardis_hum_10",
            "type": "event"
            },
            {
            "name": "tardis_hum_11"
            "type": "event"
            }
        ]
    },
    "tardis_hum_1": {
        "category": "ambient",
        "sounds": [
            {
            "name": "tardis_hum_1",
            "type": "sound",
            "stream": true
            }
        ]
    },
    etc, etc ...

[vistaero]

What is "type", "event" and "type", "sound",?

[eccentricdevotion]

I haven't actually tested anything yet, but my understanding comes from:
http://minecraft.gamepedia.com/Sounds.json
https://www.reddit.com/r/Minecraft/comments/1ont25/snapshot_13w42a_has_been_released/cctryvp

"type": "event" is calling another section of the sounds.json file, so for example it looks for the "tardis_hum_1" section and plays the sound found there

"type": "sound" just plays the specified sound file in the resource pack

[eccentricdevotion]

Actually putting "type": "sound" makes no custom sounds play at all. Hum preference added to plugin :)