Mobs idling sound
#1
Hello, Im new to cuberite, I'm currently a C developer (not really a c++ fan but I know how to write code)

Right, I know this its not a bug, but why do mobs do not emit sounds when idling? like cows, pigs etc.?

It was a decision to keep this way? Could anyone provide more details on this?

Thanks a lot
Reply
Thanks given by:
#2
Hello, welcome to the forum.

Basically no-one got around to implementing it yet.

It's not so easy as it looks. We need a kind of a SoundManager object that receives requests to play sounds and it filters the sounds so that not too many are played at the same time at the same place, and that only the mobs near to players are sent via network.
Reply
Thanks given by: polaco1782
#3
(08-11-2019, 04:16 PM)xoft Wrote: Hello, welcome to the forum.

Basically no-one got around to implementing it yet.

It's not so easy as it looks. We need a kind of a SoundManager object that receives requests to play sounds and it filters the sounds so that not too many are played at the same time at the same place, and that only the mobs near to players are sent via network.

Hello,

Thanks for your reply.

I'm studying cuberite internals, I like this kind of challenge. If I do any progress I'll open a PR.

Ah, I also built a custom debian based OS, just to run cuberite. It has a small footprint (around 400mb) and it is burn and play lol.

May I name it CuberiteOS? I'll release it soon, If I'm allowed to use it.

Thanks.
Reply
Thanks given by:
#4
Before you start writing code, it's a good idea to brainstorm publicaly. Write what you want to do, how you plan on implementing it, what kind of interface. People will chime in with additional ideas about what the code should do, what the interface needs to cover, or just general useful stuff. You may find that your original idea lacks in some ways, or would be impossible to extend later on, etc.

An entire OS for Cuberite? Now I'm scaredTongue Linux variant number 284657495. What good is it to have an entire OS just for a single server?
I don't care about the name, and we don't really have any kind of copyright over it, other than "prior art". So name it away.
Reply
Thanks given by:
#5
(08-12-2019, 10:35 AM)xoft Wrote: Before you start writing code, it's a good idea to brainstorm publicaly. Write what you want to do, how you plan on implementing it, what kind of interface. People will chime in with additional ideas about what the code should do, what the interface needs to cover, or just general useful stuff. You may find that your original idea lacks in some ways, or would be impossible to extend later on, etc.

An entire OS for Cuberite? Now I'm scaredTongue Linux variant number 284657495. What good is it to have an entire OS just for a single server?
I don't care about the name, and we don't really have any kind of copyright over it, other than "prior art". So name it away.

Okay, right now I'm just studying its code, trying to understand the implementation and messing with the code. lol.

About the OS, yes LOL, an entire distro only to run it. I work with embedded linux solutions, and I ended up creating this OS only to run it.

It is currently targeted to the RPI3, runs in 64bit mode kernel and userland (aarch64) pretty good. There is no GUI, no DE or etc, and it is easier to non-tech users to get it running,
you just burn the SD card and its done. Then the user can manage it using its web interface.

I'll push my build scripts and the pre-built version soon.
Reply
Thanks given by:




Users browsing this thread: 1 Guest(s)