irchaz20

This is the output of information I got using Claude AI. Now I understand the issue. Looking at the flow: When search has no query, the RenderUI method renders a Search Placeholder button on top of the input field (line 1750-1760) Clicking that button fires terminal.cmd search onclick (line 1751) The onclick handler calls FocusSearch() (line 175), which hides the placeholder and sets the input field to autofocus The problem is that clicking the search area triggers the button click, which sends a console command to the server. But in Rust's UI system, when the HudMenuInput input field gets autofocused, the loot panel can lose focus and close. The FocusSearch method updates the input field component with Autofocus = true and HudMenuInput = true, but this UI update can cause Rust's client to close the loot panel since the player is interacting with the HUD menu layer rather than the loot panel layer. This is a known quirk with the Terminal plugin's search — the HudMenuInput type input field, when activated via a button click that goes through the server round-trip, can cause the client's loot panel to close because the game interprets the menu input focus as leaving the loot context. Unfortunately this is a plugin-side bug in Terminal.cs itself that you'd need the plugin author (0xF) to fix. The root cause is in the interaction between CuiInputFieldComponent with HudMenuInput = true and the active loot panel. It's not something you can resolve through server config alone. Your options would be to report it to the plugin author on Codefling, or as a workaround, players can use the chat command approach to search items directly if the plugin supports one. Would you like me to check if there's a chat-based search command in the plugin? Opus 4.6