Jump to content

terorie

Members
  • Posts

    4
  • Joined

  • Last visited

Converted

  • Gender
    Male
  • URL
    https://alphakevin.club
  • Personal Text
    Average noob

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

terorie's Achievements

Tree Puncher

Tree Puncher (2/8)

0

Reputation

  1. Account created 5 minutes ago, already 5 posts with chinese letters and stuff (name is hannamza1)
  2. How embarrassing, I read that documentation at least ten times. Forge / Minecraft continues to amaze me! Thank you, I got it to work `.` – Have a nice Sunday, terorie
  3. I am porting a mod from 1.7.10 to 1.10.2. (Parts of Witchery) In a BlockXY.dropBlockAsItemWithChance (Server-side as far as I understand?), the dropped block sends a particle event and a SoundEvent to nearby players through SimpleNetworkWrapper. The author does this with a custom IMessage that instantly plays a sound in onMessage (Must be executed on client side, right?). I was breaking my head over how to implement this in 1.10.2 the last 30 minutes. Now I had three ideas how to do this in 1.10.2: Couldn't you just let the nearby clients figure our theirselves that "dropBlockAsItemWithChance" is about to be called? Then every client would play that sound locally without receiving packets that tell them specifically to play packets. Or did I get the client/server concept of Minecraft completely wrong there? If you want do it exactly like how I described it at the beginning, you would find that SoundEvents don't have a corresponding numeric ID, only resource Strings. Do I need to create an enum that maps sound Resource Strings to numeric values? {Why not} / {how to} use SPacketSoundEffect? Does it work for vanilla sounds only? Can you send the SPacketSoundEffect through the SimpleNetworkWrapper? Sorry for the nooby post, the last thing I wanted to do is annoy people in a forum. But I'm desperate, I would really appreciate some help! — terorie
×
×
  • Create New...

Important Information

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