nivex
-
Posts
5,154 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by nivex
-
I don't recall what caused this for the last person with this issue. I think it was a plugin altering stacksizes.
-
no problem. yes, if you changed your loot tables then you might want to back them up first. reinstall is the best way
-
hi, tier 3 does not include the bases from tier 1 or tier 2. each tier has its own unique bases. that is the only difference between each tier. -
Amount Of Items To Spawn in the profiles, oxide/data/RaidableBases/Profiles/ -
I gave you multiple answers what does it say when the plugin loads you need to show me what it says
-
no idea what that means. if using Carbon then you'll have to ask them.
-
rbe debug command is there to help you with issues. most common reason is not enough players online. Minimum Required Players Online is under Maintained Events and Scheduled Events in the config make sure the plugin loads without any errors. make sure the copypaste files exist. you can check by typing rb.config list make sure you see the loot files being loaded after the plugin loads
-
@Tomato_Jesus not yet, busy with other priorities. send me the config in DM and I'll check when I can
-
@Yaruani I use the native method from the game to get the grid. whether it's from the game or my own code it will never be 100% accurate you can disable Prevent Players From Hogging Raids in the config
-
no. GongJiLi should fix several issues 1. it should ignore entities not owned by a player 2. it should not modify rocket damage until explosion 3. fix exploit in OnEntityTakeDamage with GetActiveItem 4. damage is not scaled if the item is the last in the stack nice plugin but those issues are going to be difficult to fix unless he knows exactly how already. #1 sounds easy until you realize #2 has to be fixed for it to work for rockets. #3 seems very difficult since you can't use WeaponPrefab as that's often the prefab and not the entity itself (so the skinID will be 0 in this case) exploit: 1. configure skinid and attack power for rocket launcher 2. throw a grenade 3. equip the rocket launcher 4. wait for explosion 5. damage of grenade will be scaled by 300 { "skinid And attack power": { "1839729563": 300.0 } }
-
nteleportation allows characters a-z and 0-9 for sethome so passing underscore in the argument doesn't work (e.g: V3_2). I would change it, but it's been this way for over 4 years -
"Lock Raid To Buyer And Friends": false, i see you have this set false but you are letting public raids be locked with "Lock Treasure To First Attacker": true, might want to allow players to keep their raids locked since they are spawning as PVE.
-
Max Amount Of Players Allowed To Enter Each Difficulty set these back to 0 I think I forgot to fix it, and you have some of them set to 1 so it won't let anymore than 1 inside either way, don't limit it until next update. best to keep at 0
-
hi, attach your config
-
I had mine set to 0 when I used that plugin
-
@Tomato_Jesus I'll check it out. was either raid purchased?
-
it could be that Oxide reset it somehow. it's happened to a few others. I reported it but they said nothing was changed so odd that it didn't reset the nightmare profile though!
-
medium, hard and expert don't have a difficulty configured easy and nightmare do
-
hi, zip the config and oxide/data/RaidableBases folder and DM me it
-
oxide/data/RaidableBases.json file contains the both ladders and RIP =(
-
oxide may have reset the settings if that's the case you can first try by changing the difficulty back to what it should be oxide/data/RaidableBases/Profiles on the very first line,
-
good! I'll have to remember that one
-
hi, config: Lock Treasure To First Attacker Bypass Lock Treasure To First Attacker For PVE Bases Bypass Lock Treasure To First Attacker For PVP Bases Lock Raid To Buyer And Friends profiles: Eject Enemies From Purchased PVE Raids Eject Enemies From Purchased PVP Raids Eject Enemies From Locked PVE Raids Eject Enemies From Locked PVP Raids
-
I sent debug version in DM It will log the despawn reasons to oxide/logs/RaidableBases/despawn I advise you do not make any mention of this debug logging to anyone and just send the log when the issue happens again someone could be causing this to happen and we must find the exact reason without any interference
-
07/08/2023 17:48:31 Spawning raidmed7 N/A (0) @ R25 (547.9, 1.0, -1706.5) 07/08/2023 17:48:31 Init raidmed7 N/A (0) @ R25 (547.9, 1.0, -1706.5) 07/08/2023 17:48:31 Spawned 143 raidmed7 N/A (0) @ R25 (550.0, 0.0, -1700.0) Despawned 07/08/2023 18:55:16 Despawned raidmed7 vakoaa (76561198278424826) @ R25 (550.0, 0.0, -1700.0) 3 minutes later he responds 18:58 [Info] [Better Chat] [Global] [Player] vakoaa: same problem again, base disappeared during raid there are no problems shown in any logs. I will add some debug for you and send this version for you to use
