nivex
-
Posts
5,174 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by nivex
-
its not the plugin. you must have all the messages in each language file for each language that you support if using ru language primarily then you would set the server default to ru using oxide.lang ru all language API is done by Oxide using lang.GetMessage where the client language is determined by player.UserIDString if they are using Turkish and you have only English and Russian then it will use English. this is not a bug if messages do not exist in your language files then you will see the key instead. this is not a bug if your client language is set to English then you will see English. this is not a bug anyway, easier to continue using the English file since you're doing it already. -
i would need the profiles too
-
you just need to add the new language messages from English to Russian file with each update. there's no issue with having to do that since you are going to translate the new messages regardless
-
@aimacak string text = rf(Instance.lang.GetLanguage(userid) != "en" ? mx($"Mode{mode}", userid) : mx($"Mode{mode}", userid).SentenceCase()); right, I forgot people use English language file instead of their own language file. but why is that the case? change to: string text = rf(mx($"Mode{mode}", userid)); if (GetRaidableMode(text) != RaidableMode.Random) { text = text.SentenceCase(); } proper way to do this is to set the server language using oxide.lang
-
it all must use the same size its anchored to the middle center. it appears off because its a special character. ™
-
@aimacak it's using the text from your language file. ModeEasy, ModeMedium, ModeHard, ModeExpert, ModeNightmare. you have colors in those messages, so it's going to show them. string text = Instance.lang.GetLanguage(userid) != "en" ? mx($"Mode{mode}", userid) : mx($"Mode{mode}", userid).SentenceCase(); you would need to change that to: string text = rf(Instance.lang.GetLanguage(userid) != "en" ? mx($"Mode{mode}", userid) : mx($"Mode{mode}", userid).SentenceCase()); will note the flame turret down.
-
I may add it at some point- 583 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
sounds like another plugin blocking it unless you have configured to block outside damage or such
-
hi, I support this for Oxide only atm
-
well they're not supposed to reload if they don't have infinite ammo they should be given ammo one time initially though. is that what you're saying isnt happening now? how much ammo are you trying to spawn in the turret? and what is the stacksize on your server for this ammo type? @Shneid
-
@Kobaniyou need to disable Use Difficulty Colors For Buttons if you want to use your own colors. likewise disable Use Contrast Colors For Text Color if you don't want the text color adjusted.
-
@Kobani I did not say you could change the layout. you can change the position of the UI and the colors.
-
@Shneid can check it out again but I haven't had this issue no matter the size of the base. send me one of your problematic bases and Ill check it out too perhaps there's an issue with your server. you can test this by replacing turret.inventory.AddItem(attachedWeapon.primaryMagazine.ammoType, p, 0uL); with turret.inventory.AddItem(attachedWeapon.primaryMagazine.ammoType, p, 0uL, ItemContainer.LimitStack.None); @Sahyatt config, to lock bases to the player, and the time it will reset after they become inactive: "Bypass Lock Treasure To First Attacker For PVE Bases": false, "Bypass Lock Treasure To First Attacker For PVP Bases": false, "Lock Treasure To First Attacker": true, "Lock Treasure Max Inactive Time (Minutes)": 20.0, "Lock Players To Raid Base After Entering Zone": false, you setup the eject settings in the profiles: "Eject Enemies From Purchased PVE Raids": true, "Eject Enemies From Purchased PVP Raids": false, "Eject Enemies From Locked PVE Raids": true, "Eject Enemies From Locked PVP Raids": false, @byond1991 disable Allow Friendly Fire in the profiles
-
@Dr.D.Bug seems you're not using 2.6.9 as i'm no longer able to reproduce your issues using the provided config I tested, and the cooldown was set a second time when the raid was completed, making it impossible to buy another before the base despawned. I tested with 4 zones and allowed 1 in the config. it blocked 3 zones and it allowed the 1 that I configured. 2 zones had a radius and 2 had a size to be as thorough as possible if you want to set me up an account and provided your server details then I'll gladly test this myself on your server
-
fixed in next update, change both instances of bool deployables, bool structures to bool structures, bool deployables change one instance of deployables, structures to structures, deployables
-
I will not change it back. you can change the offsets and colors in the config just as you could before.
-
@byond1991thats not the latest version. the latest is 2.6.9. not sure what you did with your setup, but no loot tables loaded either, and the plugin cannot reset it either. use rbe debug when you have issues with your config/profiles
-
1x - 1x building is unavailable: Gard Purchase
nivex replied to P.L Isolation's Support Request in Support
copypaste files need to go in oxide/data/copypaste folder it needs to be lowercase you need a profile with the difficulty set to 1 and 2 in order to use medium and hard other than that idk. type rb.config list -
@AvG ЛаймонI too am confused. beyond a few small optional changes each update I don't know what you could be referring to. but don't fret, new updates will consist of improvements to existing functionality, with a few QOL options when they're useful, and of course bug fixes because Im a pro at breaking stuff. @byond1991no changes were made to spawns except for zone manager, everything else is UI related. check what the plugin says when it loads. how many zones were allowed, blocked, and how many points are on the grid after the grid finishes loading? if that looks good then use rbe debug. it is there to tell you whats wrong with your config/profiles. type it again to toggle it off once you get the messages. look at how frequently a message was, and then determine the most likely cause. those messages are good and bad. its debug and should be easy enough to understand as most of the messages are self-explanatory.
-
2.6.9 released. please mention any previous issues again if they still happen in this version. be as specific as possible
-
@Thunderchilehey there, flame turret and shotgun traps are immune to fire damage in vanilla @KingSizeKevinhey there, players should not receive a lockout for purchased bases anymore. that was a bug. it should not use the lockout UI for buyable cooldowns anymore either. players receive a lockout for regular raids. they may receive a buyable cooldown for a regular raid which is a bug and is fixed in the next update. there is a lockout UI for this players receive a buyable cooldown for purchased raids. there is no UI for this, but one is added in the next update there is an issue where a player can buy another raid after a raid is completed but before it despawns. this is fixed in the next update. thankyou @Dr.D.Bugfor answering!
-
I still take damage using your TruePVE config
-
ok, ill check it out
-
wasn't able to reproduce this. maybe post your TruePVE config and ill see if RB is not handling it like it should.
