nivex
-
Posts
5,177 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by nivex
-
yes you need to update copypaste as aimacak said -
hi, I do not know what is causing the issue yet but this is good information ty for sharing.
-
@m3dus4 heya, set Lock Players To Raid Base After Entering Zone false set Prevent Players From Hogging Raids to false otherwise you need to be more specific if this doesn't work.
-
there has to be some error or it would be working zip your server log, oxide/data/RaidableBases/ folder and oxide/data/copypaste/ folder and DM it to me (dont post it in the ticket)
-
so its not the map marker it would be something else causing all of that. errors in server console? I would need server logs
-
"Radius": 0.25, this should be 0.35 "Radius (Map Size 3600 Or Less)": 0.25, this should be 0.5 no idea why the marker doesn't show. it definitely works fine
-
@aimacak No. I have stated this numerous times. I will help you with your special issue when I can so be patient @MNfreakTim thanks, added a check in next update.
-
no problem. I just want everyone to understand that my plugins have a lot of complex features in them and some of those features take or have taken a lot of time, patience and testing to be implemented properly, such as this one in regards to the issues with entity lookup. I am not that great at it either so that makes it take longer =p
-
@RustyW that would be very very bad for any servers that accidentally enabled that option. not only that, imagine being an active player and your base despawns because the TC owner was inactive. I'd be very mad. it would cause more problems than it would solve.- 583 comments
-
- 2
-
-
- #rust
- #rust plugin
- (and 6 more)
-
Changed Status from Pending to Closed Changed Fixed In to Next Version
-
Changed Status from Pending to Closed
-
thanks. i've excluded player owned entities (bradley/heli) in next update. what bugs "fix all the bugs" ? ive responded to your door and tc issue which isn't caused by this plugin. that leaves 1 issue with performance and that pertains to large bases only. it must be extensively tested before I release it and it will not be released until it is tested on live servers and confirmed to be working without any exceptions. it is complicated as it must find all entities of the base without getting any bases or entities belonging to active players. there is no easy way to do this. the games building manager is not sufficient for this as 1 tc = 1 building and that excludes various entities which must be accounted for during conversion too. it is extremely complicated unlike CopyPaste where it just copies everything irrespective of ownership. if it were easy i wouldn't still be working on it
-
yes anyone with twig issue needs to update copypaste to 4.1.36+ ty nashslash
-
i can note this down.
-
heya. there's no way to protect this entity after the base despawns, and Prevent Looting plugin does not protect that entity (it protects item_drop_backpack) the only option available is to despawn it, Despawn Dropped Loot Bags From Raid Boxes When Base Despawns
-
i'll check it out later @Dr.D.Bugbut it worked just fine in my testing. nothing spawned outside of it when only allowed inside, and vis versa @sinansisno, wooden stone metal hqm are in the profiles under Change Building Material Tier To. adobe will not be supported until copypaste plugin supports it. @Killerooxrust must fix this. they're aware and will fix it when they can.
-
yes, the base timer resets if you do not use the plugin for at least 24 hours, and it resets when the server wipes. it does not reset at any other time unless the player is active or has someone active
-
Bases dissappeared from list and stopped spawning
nivex replied to CyberCity892's Support Request in Support
if hard isn't available then it has a json error. check the server console when the plugin loads and put the file into a json validator such as jsonlint.com oxide/data/RaidableBases/Profiles/Hard Bases.json this is not for buyable events. it is for maintained and scheduled. so you can set expert and nightmare to -1 "Max Amount Allowed To Automatically Spawn Per Difficulty (0 = infinite, -1 = disabled)": { "Allow Max Amount Increase From Difficulties Disabled On A Specific Day Of The Week": false, "Easy": 2, "Medium": 2, "Hard": 2, "Expert": 1, "Nightmare": 1 }, this is for buyable events. so they will be able to buy them still. "Max Amount Purchasable Per Difficulty (0 = infinite, -1 = disabled)": { "Easy": 0, "Medium": 0, "Hard": 0, "Expert": 0, "Nightmare": 0 }, -
"Rewards": { "Custom Currency": { "Enabled": false, "Item Shortname": "scrap", "Item Name": null, "Amount": 0, "Skin": 0 }, "Economics Money": 0.0, "ServerRewards Points": 0, "SkillTree XP": 0.0, "Do Not Reward Buyable Events": false }, hi. yes, you can do so in the profiles oxide/data/RaidableBases/Profiles/
-
@Kapco411 I just spawned 200 bases for you using Maintained Events to test this, and I looked at each and there were no issues regarding this there were no changes regarding this in the last update either. I have received several reports of the difficulty, and only the difficulty, resetting in each of the profiles to 0 which is Easy. nothing was changed regarding that, and it cannot reset on its own. I suspect a json conversion issue in Oxide but I've not been able to reproduce it myself. if you want to zip these files and DM them to me in a private message then I can look into it further for you. oxide/data/copypaste/ but do not include any paid content from other vendors oxide/data/RaidableBases/ oxide/config/RaidableBases.json it is most likely that you have a few bases in the wrong profiles. this is a common issue with some third party base packages.
-
i was not able to strike the base with Allow Players To Use MLRS set to false as seen by the "You are not allowed to target this location!" messages next i moved the strike zone outside of the boundary, and the impact area was not close enough to damage the base either which you can see by the dust cloud in the center of the image so it may be SkillTree or something else, but we've tested it before and it worked just fine with that too verify that Allow Players To Use MLRS is actually set false in those profiles, and that the difficulty is set properly (very first setting of each profile) too
-
@Stark ill check it out
-
i'll have to add more specific messages for these issues then =p
-
@406_Gromit haha that sounds awesome. how is it on performance though?
-
make sure difficulty is set properly in each profile, oxide/data/RaidableBases/Profiles/ otherwise either install the copypaste files, or if they exist then add them to the profiles if using my package then just reinstall it if you can't figure it out.
