Jump to content

Ryuk_

Creator
  • Posts

    455
  • Joined

  • Last visited

Everything posted by Ryuk_

  1. Ryuk_

    2.0 bugs.

    Hey! that problem is already solved, it was caused by the new "creative" in game commands, by default are all set false, but if you don't change your config or doesn't restart the server you should send the commands creative.allUsers false creative.freePlacement false creative.freeBuild false creative.freeRepair false
  2. Ryuk_

    plugin not working with oxide

    Please try the latest update, also remove the config file first
  3. Ryuk_

    Decay error

    Changed Status from Work in Progress to Closed
  4. Ryuk_

    Item remove

    Changed Status from Work in Progress to Closed
  5. Ryuk_

    plugin not working with oxide

    The update is out, all related bugs should be fixed now. Please take a look and give feedback if you can. I will close the ticket in 1 day if there is no response. 2.0 Version was already working on oxide.
  6. Ryuk_

    2.0 bugs.

    The update is out, all related bugs should be fixed now. Please take a look and give feedback if you can. I will close the ticket in 1 day if there is no response. 2.0 Version was already working on oxide.
  7. Ryuk_

    My sql issues

    The update is out, all related bugs should be fixed now. Please take a look and give feedback if you can. I will close the ticket in 1 day if there is no response. 2.0 Version was already working on oxide.
  8. Ryuk_

    Item remove

    Changed Status from Pending to Work in Progress Changed Fixed In to 2.0.1
  9. Ryuk_

    Decay error

    Changed Status from Pending to Work in Progress Changed Fixed In to 2.0.1
  10. Ryuk_

    plugin not working with oxide

    Changed Status from Pending to Work in Progress Changed Fixed In to 2.0.1
  11. Ryuk_

    2.0 bugs.

    Changed Status from Pending to Work in Progress Changed Fixed In to 2.0.1
  12. Ryuk_

    My sql issues

    Changed Status from Pending to Work in Progress Changed Fixed In to 2.0.1
  13. Ryuk_

    Bgrade not Working

    The update is out, all related bugs should be fixed now. Please take a look and give feedback if you can. I will close the ticket in 1 day if there is no response.
  14. Ryuk_

    Bgrade not Working

    Changed Status from Pending to Work in Progress Changed Fixed In to 2.0.1
  15. Ryuk_

    Broken after forcewipe

    Hey! how are you, currently it's the version 1.0.19 you're using the 1.0.17 Anyways i will release a new update in a moment, so make sure to update the plugin.
  16. Ryuk_

    2.0 bugs.

    Hi! Community tab require SQL connection in order to work can you please send a video of the following things? Doors gets bugged when using auto place, u only see handle. u can build foundations into eachother overlapping. bgrade dont work, it starts in the right grade i selected but finishes as twig.
  17. Ryuk_

    Symmetry not symmetrical

    Hello! Can you see if when you center the symmetry, it is correctly in the center? A colored circle will appear in the center to guide you.
  18. Ryuk_

    Symmetry not symmetrical

    Changed Status from Pending to Work in Progress Changed Fixed In to 1.0.19
  19. It was supposed to be updated this week but it is being tested and some bugs have been found, I hope they are the last ones. In 1/2 days I will send the new version to the guys who are testing it and if everything is perfect I should update it on MONDAY. I also have to record a video demonstrating how to use the new features and configure it, plus update the whole description. One of the problems solved was that it only worked with CARBON and was not compatible with OXIDE (solved now).
  20. using System; using System.Collections.Generic; using UnityEngine; namespace Oxide.Plugins { [Info("ChinookCrate", "Ryuk", "1.0.0")] [Description("Remove hackable crate when the chinook drops it.")] public class ChinookCrate : RustPlugin { void OnCrateDropped(HackableLockedCrate crate) { NextTick(() => { if (crate != null && !crate.IsDestroyed) { if (IsChinookNearby(crate.transform.position, 20f)) { crate.Kill(); } } }); } private bool IsChinookNearby(Vector3 position, float radius) { var entities = new List<BaseEntity>(); Vis.Entities(position, radius, entities, Rust.Layers.Mask.Vehicle_World); foreach (var entity in entities) { if (entity is CH47Helicopter) { return true; } } return false; } } }
  21. Ryuk_

    Building Symmetry

    That could be a terrain check problem, I will take a look and see if I can fix it
  22. Yes, copy the latest code i sent and paste it into "ChinookCrate.cs"
  23. Just replace the plugin name Chinook_Crate_Event to ChinookCrate i don't know why you get that error if the main class and the name is the same... // https://codefling.com/ryuk_ using System; using System.Collections.Generic; using UnityEngine; namespace Oxide.Plugins { [Info("ChinookCrate", "Ryuk", "1.0.0")] [Description("Remove hackable crate when the chinook drops it.")] public class ChinookCrate : RustPlugin { void OnCrateDropped(HackableLockedCrate crate) { NextTick(() => { if (crate != null && !crate.IsDestroyed) { crate.Kill(); } }); } } }
  24. This only works for removing the locked hackable crate when the chinook drops it. I don't know how to allow the players to lock the entity using the homing missile launcher sadly
  25. This should work and prevent the crate from spawning without removing the chinook from the game // https://codefling.com/ryuk_ using System; using System.Collections.Generic; using UnityEngine; namespace Oxide.Plugins { [Info("Chinook_Crate_Event", "Ryuk", "1.0.0")] class Chinook_Crate_Event : RustPlugin { void OnCrateDropped(HackableLockedCrate crate) { NextTick(() => { if (crate != null && !crate.IsDestroyed) { crate.Kill(); } }); } } }
2.1m

Downloads

Total number of downloads.

9.7k

Customers

Total customers served.

140.9k

Files Sold

Total number of files sold.

3m

Payments Processed

Total payments processed.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.