ninco90
-
Posts
691 -
Joined
-
Last visited
-
Days Won
4
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by ninco90
-
Hello! The author has informed me of the problem. When changing the TC skin, the new TC doesn't connect to that moving building. That's the problem. We'll investigate and see what we can do.- 421 comments
-
- 1
-
-
- #builder
- #automation
- (and 9 more)
-
You need to be careful and add some option to the configuration to not award paid items, as doing so would violate FacePunch's new terms and conditions, which will apply starting in August.- 14 comments
-
- 1
-
-
- #random loot
- #random items
- (and 3 more)
-
Hi! You can edit the upgrade or repair speed in the config. "Cooldown Frequency Upgrade (larger number is slower)": { "bettertc.use": 0.1, "bettertc.vip": 0.1 }, "Cooldown Frequency Reskin (larger number is slower)": { "bettertc.use": 0.1, "bettertc.vip": 0.1 }, "Cooldown Frequency Repair (larger number is slower)": { "bettertc.use": 0.1, "bettertc.vip": 0.1 }, "Cooldown Frequency Wallpaper (larger number is slower)": { "bettertc.use": 0.1, "bettertc.vip": 0.1 }, However, I don't recommend setting it too fast, as in large builds, it could cause minor lag for players near the area and a small FPS spike on the server. That's why the ideal, and I think the point of this plugin, is that it improves gradually. Unlike other plugins like /up/down, which change the entire build.
-
Because there's a skin called that, and my system confused it with the item. It's now fixed. I've also reviewed all approved skins to avoid any further confusion. -
Thank you very much, that's what we're here for!
-
{ "items": { "gates.external.high.adobe_0": { "shortname": "gates.external.high.adobe", "customIcon": null, "amount": 64, "skinId": 0, "isBp": false, "category": 9, "displayName": "High External Adobe Gate", "cost": 100, "cooldown": 0 }, } It seems to work like this, although I noticed that it doesn't seem to process large jsons properly. Feel free to send me the file privately on Discord if you'd like for me to review.
-
Curious. I just noticed a false positive; "table" is a normal, free item in the game. I've already fixed it.
-
Try it now and tell me.
-
I made some improvements, now you can validate by fields.
-
Ahh, now I understand. What this does is search for any numerical matches to adapt to different use cases. That's why if another variable, like amount, has a numerical match, this appears. I'll try to figure out how to filter better or even make it possible to select only the field to validate. Thanks for the information!
-
Hi! What's not matching exactly? My tool uses the RustHelp API, where one of its developers currently works for Facepunch. This API collects both Steam store items and approved skins. I believe the list also includes items that were never released or were deleted for some reason but exist hidden on Steam.
-
That's correct, nothing else needs to be done. Just leave the new configuration as false by default. There's a bug when displaying purchased wallpapers; I'm working on it.
- 421 comments
-
- 2
-
-
-
- #builder
- #automation
- (and 9 more)
-
Of course, having it enabled in the global settings completely disables the automatic wallpaper removal system. But of course, then in the TC you only set one face (i.e., like in vanilla), and for some reason it applies a default wallpaper to the other side of the face. I'll check this to see if it causes the same problem and I can solve it. Yes, but this would apply to all walls, including the ones inside the foundation. I don't know if I'm explaining myself correctly.
-
Hi! If you've disabled the "both sides" option in your settings before the wipe, you shouldn't see any wallpapers on the exterior sides. When this setting is set to true, what it does is override the game's internal wallpaper override system when the wall is built. It has a system programmed to constantly check if there might be a wallpaper on the exterior to automatically remove it. My setting overrides this checking system in the game itself. What I find curious is that the default wallpaper randomly appears on building blocks. Maybe when something is built very close to said wall? Maybe the game checks to apply wallpapers to the other side of the wall if it has a roof or something similar. I'll definitely have to investigate this further, but I don't know if I can find a 100% valid solution, since what we're doing is overriding the game's default behavior by enabling this "both sides" setting.
-
Strange, I personally use Carbon on both the staging server and my x5 and have never encountered this problem. It sounds like a compatibility issue with another plugin. You could try without the rest of the plugins and reload BetterTC as you add plugins until you figure out where the problem is.
-
Implemented in 1.5.3 thanks to @BoobleJ
- 421 comments
-
- 1
-
-
- #builder
- #automation
- (and 9 more)
-
Facepunch changed the item to which the wall wallpapers are applied. Therefore, existing custom wallpapers (before the update) are no longer compatible unless they are regenerated or updated. In my case, I updated the existing wallpapers. The problem with this is that Steam Workshop updates don't usually handle it very well. So, when a change is applied, it either takes a long time to update in the background, or it doesn't update at all, or it updates quickly. You'll find a list of all the SkinIDs in the BetterTC data file. You can search for them manually and delete them, or simply wait for Steam to force a content update at some point so the changes are applied and then displayed correctly in the game. Unfortunately, there's no command to force this to happen. Honestly, it's a bit of a pain. I should have created new items instead of updating the existing ones; I thought it would have caused fewer problems.
-
Wallpaper designs are loaded through the workshop; it has nothing to do with the image library. You may have old files on your computer, as the wallpapers have been updated internally. I suggest waiting for Rust to update them internally or forcing them to update by manually clearing them from the workshop cache on Windows. Example: C:\Program Files (x86)\Steam\steamapps\workshop
