-
Posts
48 -
Joined
-
Days Won
3
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Reels
Support Center
Everything posted by Neko
-
Changed Status from Pending to No Response
-
need help setting up to bot for my discord and sever
Neko replied to snowyyproject's Support Report in Support
Changed Status from Pending to No Response -
Changed Status from Work in Progress to Can't Reproduce
-
After testing on a fresh server, I wasn't able to replicate this issue with personal time changes. I did find a separate issue with specifying a position from RCON which will be fixed in v1.0.2. Could you please tell me: Does envcontrol.time <steamid> display the expected time that the player should be seeing, after they have changed it? Are you using Oxide or Carbon? Are you using any other plugins with similar functionality which may conflict? Exactly which commands are failing and are you running them through chat, console, or rcon?
-
Changed Status from Pending to Work in Progress Changed Fixed In to Next Version
-
Hi thank you for letting me know, I will take a look asap
-
- 2 comments
-
- 1
-
-
- #environment
- #day
- (and 5 more)
-
Version 1.0.0
27 downloads
EnvControl is a Rust plugin that provides per-player control over in-game time. Players and administrators can lock, set, or reset each player’s time environment — giving everyone the freedom to experience the world at their preferred time of day. Perfect for VIP perks, roleplay scenarios, testing environments, and custom minigames where players may want a unique lighting experience without affecting others. Key Features: Individual time control per player Allow players to choose their own time Force players to see a specific time based on group Automatically applies locked times on connect Config { "Permission-based custom times for player (24hr e.g. 07:00, 18:30)": { "envcontrol.vip": [ "15:00", "18:00", "21:00" ], "envcontrol.day": [ "12:00", "13:00" ] }, "Permission-based forced time for players (applied on connect)": { "envcontrol.night": "23:00", "envcontrol.morning": "07:00" } } Users with a permission from Permission-based custom times for player can use the /env command to set the time. Groups can stack and can contain overlapping times. Users with a permission from Permission-based forced time for players cannot use the /env command unless they have a permission from Permission-based custom times for player. When a player’s time is reset, the plugin checks whether they have a permission-based time lock. If a matching permission is found, their time is set accordingly. Otherwise, they revert to the server’s default time. Commands /env Sets your personal environment time using a 24-hour format. Example: /env 18:00 — Locks your view to evening lighting. /env list Displays all available times you can set, based on your permissions. /env reset Resets your personal time back to the default value, or to your group’s forced time if applicable. Requires envcontrol.reset envcontrol.reload Reloads the plugin configuration file. Requires envcontrol.admin Example: envcontrol.reload envcontrol.time <steamid> (time) Gets or sets a player’s locked time. Works for connected & disconnected players. Requires envcontrol.admin Example: envcontrol.time 76561198000000000 18:30 — Locks that player’s time to 18:30. envcontrol.time 76561198000000000 — Displays the player’s current locked time. envcontrol.reset <steamid> Resets a player’s time to their default value. Requires envcontrol.admin Example: envcontrol.reset 76561198000000000 envcontrol.radius <radius> <time> (x,y,z) Locks time for all players within a specific radius. Requires envcontrol.admin Example (in-game): envcontrol.radius 30 21:00 — Locks nearby players to 21:00. Example (RCON): envcontrol.radius 50 12:00 500,100,-200 — Locks nearby players to 12:00 at coordinates 500,100,-200. Permissions envcontrol.admin Provides full control over all console commands and time management features. Allows any time to be passed to /env envcontrol.reset Allows players to use the /env reset sub-command. Custom Time Groups Defines which time values specific permission groups can manually select. For example, players in a VIP group might be able to set 15:00 or 18:00. These are automatically registered based on your config. Forced Time Groups Automatically applies a fixed time to players when they connect. For example, members with “envcontrol.night” might be setup to see 23:00 on login. These are automatically registered based on your config. AI Disclaimer This product was created with the help of AI tools to enhance quality and clarity. The full extent of AI assistance is as follows: Language messages: Default in-game messages were refined for consistency, clarity, and professional tone. Product description: The plugin description was enhanced for readability and better presentation of key features.$5.00- 2 comments
-
- #environment
- #day
- (and 5 more)
-
Changed Status from Work in Progress to Fixed
-
need help setting up to bot for my discord and sever
Neko replied to snowyyproject's Support Report in Support
Installation Instructions - Website: https://codefling.com/discord-bots/discord-pop-bot - Support: https://codefling.com/discord-bots/discord-pop-bot?tab=support MANUAL INSTALLATION These instructions are for users who want to run the script manually on a VPS or Dedicated Server. 1. Ensure Python is installed from https://python.org/downloads 2. Configure your bots by creating a new JSON file in the "Bots" folder for each bot you intend to run. Refer to the "examples" folder for guidance. 3. Install all required dependencies using "pip install -r requirements.txt" 4. Execute "run.py" using "python run.py" in the console. Note: certain managed systems may require alternate or partial commands. 5. Review any errors or logs thoroughly to identify and resolve possible issues. MANAGED INSTALLATION These instructions are for users who want to run the script automatically using a managed bot panel. 1. Upload all the files and folders from the pop bot to your bot's file system. 2. Configure your bots by creating a new JSON file in the "Bots" folder for each bot you intend to run. Refer to the "examples" folder for guidance. 3. Select "run.py" as the start file 4. Review any errors or logs thoroughly to identify and resolve possible issues. If these instructions don't help get you setup just let me know. Thanks! -
need help setting up to bot for my discord and sever
Neko replied to snowyyproject's Support Report in Support
What operating system / environment are you trying to run the bot on? Using a website, your own machine, etc -
Changed Status from Pending to Fixed Changed Fixed In to Next Version
-
Hi there, apologies for the delay in getting back to you. it appears that the original place I hosted my documentation no longer exists. I'll update the zip to include a file copy. For your convenience I have included the installation instructions below. Installation Instructions - Website: https://codefling.com/discord-bots/discord-pop-bot - Support: https://codefling.com/discord-bots/discord-pop-bot?tab=support MANUAL INSTALLATION These instructions are for users who want to run the script manually on a VPS or Dedicated Server. 1. Ensure Python is installed from https://python.org/downloads 2. Configure your bots by creating a new JSON file in the "Bots" folder for each bot you intend to run. Refer to the "examples" folder for guidance. 3. Install all required dependencies using "pip install -r requirements.txt" 4. Execute "run.py" using "python run.py" in the console. Note: certain managed systems may require alternate or partial commands. 5. Review any errors or logs thoroughly to identify and resolve possible issues. MANAGED INSTALLATION These instructions are for users who want to run the script automatically using a managed bot panel. 1. Upload all the files and folders from the pop bot to your bot's file system. 2. Configure your bots by creating a new JSON file in the "Bots" folder for each bot you intend to run. Refer to the "examples" folder for guidance. 3. Select "run.py" as the start file 4. Review any errors or logs thoroughly to identify and resolve possible issues. Thanks, Neko
-
Changed Status from Pending to Work in Progress Changed Fixed In to Next Version
-
Thanks for making me aware of this. As this is a fairly low prio issue I cannot provide an ETA for when this will be fixed. In the meantime, if it is getting on your nerves, then you can fix it on your server by replacing "1.0.0" with "1.0.1" within the [Info(...)] attribute.
-
Changed Status from Pending to Closed Changed Fixed In to 1.0.0
-
Hi, I believe you've been in touch with me via Discord so will be closing the support request here and work to resolve this through our DMs. If this is not the case please let me know and I'll update the status as soon as possible. Thanks
-
Because you are running from `C:\Windows\System32\cmd.exe`, which is not where the script is located.
-
Please add `--linkage ELF` to the end of your startup command, i.e: `python run.py --linkage ELF`
-
Changed Status from Pending to Can't Reproduce
-
Hey there, This plugin uses the OnNewSave hook from uMod, and if that fails to be called for some reason then unfortunately the plugin won't work as expected. Personally, I've never experienced the hook not calling after deleting all of the files you mentioned. It's possible this is a one-off issue with Oxide, but as a temporary solutiom you can manually alter the data file's last wipe date and reload the plugin
-
I'd say 2 weeks, ish. Apologies if you're really in need of this sooner.
-
Great idea, I'm working on other products right now however I should have some time to do this in a few weeks
-
Changed Status from Pending to Not a Bug
-
Changed Status from Pending to Not a Bug