Wild Shadow

no plugin, native of the game https://www.corrosionhour.com/rust-clan-system-guide/ It shows up as channel 5 on the console; I don't know if that helps.

Hi Mercury, I noticed that the clan chat wasn't working when IQchat was loaded.

@Simil3x CommunityEntity.ServerInstance.ClientRPC<string>(RpcTarget.Player("AddUI", connection), json);

Hey ViolationHandler.exe, Hru ? Failed to compile: The non-generic method 'BaseEntity.ClientRPC(RpcTarget)' cannot be used with type arguments | Line: 9482, Pos: 31

Hey Khan, Hru ? Failed to compile: The non-generic method 'BaseEntity.ClientRPC(RpcTarget)' cannot be used with type arguments | Line: 47, Pos: 24

Failed to compile: 'CommunityEntity' does not contain a definition for 'ClientRPCEx' and no accessible extension method 'ClientRPCEx' accepting a first argument of type 'CommunityEntity' could be found (are you missing a using directive or an assembly reference?) | Line: 7361, Pos: 52

StaticTrader - Failed to compile: 'BasePlayer' does not contain a definition for 'ClientRPCPlayer' and no accessible extension method 'ClientRPCPlayer' accepting a first argument of type 'BasePlayer' could be found (are you missing a using directive or an assembly reference?) | Line: 1541, Pos: 12

Hi @Tryhard, how to add the both large furnace with the same permissions, without creating duplicates? { "Custom Placeable Entities": [ { "PrefabName": "assets/prefabs/deployable/furnace.large/furnace.large.prefab", "ItemID": -1992717673, "PlacementDistance": 2.2, "Permission": "indoorfurnace.largefurnace", "skinID": 0 }, { "PrefabName": "assets/prefabs/deployable/furnace.large/skins/industrial_large_furnace/industrial.furnace.large.prefab", "ItemID": 1868984394, "PlacementDistance": 2.2, "Permission": "indoorfurnace.largefurnace", "skinID": 0 }, { "PrefabName": "assets/prefabs/deployable/oil refinery/refinery_small_deployed.prefab", "ItemID": -1293296287, "PlacementDistance": 1.0, "Permission": "indoorfurnace.refinery", "skinID": 0 } ] } = [Indoor Furnace] Automatically Harmony patched 'WireTool.SharesRootParent_Patch1' method. (SharesRootParentPatch) Duplicate permission registered 'indoorfurnace.largefurnace' (by plugin 'Indoor Furnace') Loaded plugin Indoor Furnace v2.1.3 by Tryhard Since I'm using it in SkillTree, it bothers me a bit that it's split into two permissions, because it shows up in the buff info

I have the same problem, is the plugin still being maintained? Exception while calling NextTick callback (NullReferenceException: Object reference not set to an instance of an object) at Oxide.Plugins.HitDamage.SetFlag (BasePlayer player, System.Boolean setTo) [0x0000f] in <29c471d38f0941eb9da7778fee455a1d>:0 at Oxide.Plugins.HitDamage+<>c__DisplayClass5_0.<OnEntityTakeDamage>b__0 () [0x000f5] in <29c471d38f0941eb9da7778fee455a1d>:0 at Oxide.Core.OxideMod.OnFrame (System.Single delta) [0x00051] in <15f61ddda771464d8246ebdce8ff4811>:0

Hey Mevent Team Error while compiling UltimateCases: ) expected | Line: 9321, Pos: 54

Changed Status from Pending to Closed

Changed Fixed In to Next Version

Hello, just to let you know that in CS the version is still noted as 1.3.6

Changed Status from Work in Progress to Fixed

Changed Status from Pending to Work in Progress Changed Fixed In to Next Version

I suggest allowing users who have purchased the product to leave a quick reaction on a specific version. These reactions could then be aggregated into an average and contribute to the overall rating of the product. This approach could help gather more feedback, as leaving a quick reaction takes far less time than writing a full review. For example, when users receive a notification about a product update, they could be redirected directly to the changelog page and leave a quick reaction on that version. Of course, these version-specific reactions would only be available to users who have purchased the product. On a related note, it would also be useful to display the version number when a user writes a review for a product.

Hello, It would be helpful to be able to add a specific reaction to a particular version, rather than applying it to the entire product. This would allow for more precise feedback directly related to the changes or fixes in a given version.

Wrong Number of Version