nivex
-
Posts
5,446 -
Joined
-
Last visited
-
Days Won
190
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by nivex
-
Changed Status from Pending to Closed
-
Changed Status from Pending to Closed
-
this is now in the language file as of 2.1.4, closing this
-
Changed Status from Pending to Closed
-
normal tier is in the free version available on umod only. please read the patch notes before updating. premium plugin updates must be installed from this site only. there are no difficulty, player lockouts or buyable event options in the free version, and so installing the free version has removed these options from your installation. installing the premium version won't work either as it will recreate these settings using their default values. therefore you must reinstall the package, and then install the premium plugin last if it says you're banned then it's not revoked -
I'll take a look, but honestly just move it to a different tier if you don't like the tier it's in. everyone has their own opinion of how hard something is
-
even better, with 2.1.4 the option Send Messages To Player will do this. set it false
-
check again bud. they're all there under Event Messages in the config
-
players must be actively raiding to receive rewards. if they become inactive (Lock Treasure Max Inactive Time (Minutes)) then they will not get them. simply being present does not count as being active. to be active you must be eco raiding, using explosives or shooting the building or npcs. ladder must be enabled, and points must be configured above 0
-
@KingSizeKevincan you verify its up to date. I mean I just don't know what else to do here. There's nothing wrong with the code, and this issue is only happening on linux machines afaik
-
Event Messages in the config. Please read the documentation
-
no, I just read it wrong. no, it is likely an issue specific to Linux. I know if libgdiplus is not installed on the machine then the plugin will experience all kinds of issues, and I suspect something similar here with a missing library file or one that needs updated
-
I'm not sure, I think sending them faster would only cause more issues, but worth trying I guess. Are you using linux or windows host machine?
-
I've finally tracked this issue down and fixed it. In short, the game bugs out during the teleport and incorrectly tells the plugin that players are entering the base instead of leaving it. Due to this and players being asleep while teleporting the plugin calls code that under normal conditions would only be called one time when the base spawned. This setting is Eject Sleepers Before Spawning Base. Set this false to avoid this issue from happening until I release 2.1.4. -
np. if it's not in the language file then you cannot change it, such as the order of words shown on the map markers label. you can only edit the words themselves. I'll add the format in the language file to allow this colors are in the config and labeled as Difficulty Colors Border and Inner. If you use an invalid color then it will default to the original color. different tiers do not have different options. they have more bases
-
I cannot help you with this. You must contact an admin @Death @Steenamaroo
-
hi, you need to elaborate. cannot be looted can be explained in so many different ways. be specific pls
-
hi, you can edit the messages in the language file. oxide/lang/en/RaidableBases/
-
Set it to 5000 - I will likely remove the option since most maps cannot support it anymore. The message is self explanatory
-
depends what you changed to start with. i'd also need the map and location on the map this happened at. bases spawning that far under terrain should never happen because they are all copied perfectly where every single base has the foundation copied 1 meter (of 3) off the ground. maybe there's some Rust layer I don't know about.
-
@ZEODEthat update was released a month ago, and you downloaded it the day it was released post a screenshot inside and outside of the base, or a video short of placing boxes on top of objects to elevate them off of the ground such as on the 2nd shelf only, or make-shift shelves, i doubt this is fixable.
-
The former, but it's bugged. I accidentally set a couple variables private so they're not stored in the data file and therefore it's not tracked properly. That's fixed in the next update. -
yep
-
buyable events and maintained events spawn the same. if it isn't working then there's no more terrain for that protection radius to spawn on. the message tells you how to adjust this, by lowering the protection radius. you can create flat land on your maps using RustEdit so you do not have this issue moving forward. most custom maps do not have enough flat land, and a lot of proc gen maps concentrate flat land near water as per documentation this is not recommended and not supported. players should use the /buyraid command. if you insist on doing this you can try setting the price to 1 in the shop, the actual cost in the raid bases config, and using the command 0 = easy, 1 = medium, etc. the actual syntax ($player.id) to use is in the shop or stores plugin documentation
-
Changed Status from Pending to Closed
