Custom extension feature question: Is this tooltip feature against any rules?

I made a small tooltip feature that shows some basic buttons whenever you hover over a material. These tooltip buttons, Info, Chart… open those buffers. I know the ToS says a lot about “Premium features and services” and was wondering if this kind of custom feature would be in violation of anything related to that. I’ve read through some of the ToS but wanted to ask permission just to make sure.

I can answer questions if anything is vague or I can change something if needed.

I have a few pictures to show my tooltip:

The general rule is that extension cannot interact with the server directly, e.g. performing actions, fetching data etc.

In your case, what happens when one clicks on a button in the pop-up? You are creating a new buffer, pre-filled with a command and then the game loads that command?

A person wanting to open a new buffer would click the new buffer button, input their command, and hit enter. This is precisely what the extension does and it acts purely on the clients HTML. When you click any of the 5 buttons, the javascript does the following:

  1. Find the new buffer button, it has an html id “TOUR_TARGET_BUTTON_BUFFER_NEW” and class, and ‘click’ event.
  2. Call that event with “.click()” (clicking “NEW BFR”)
  3. Wait for an update to the node tree (opens new buffer window), and grab that element
  4. Grab the “input” element inside this new buffer window, which is wrapped by a “form” element
  5. Enter the command for the button you pressed into this input element
  6. Call the event “.requestSubmit()” on that form (hitting enter button)
  7. All done!

The code for this will be public and visible to all on github if approved.

We just talked about this in our weekly meeting and we will allow the tooltip. As long as the tooltip only opens one buffer (and consequently one command) at a time, and this happens manually, we are fine with it.

1 Like

Thanks. The tooltip opens, you click a button, it disappears. I’ll be sure to preserve this behavior.
one_click_tooltip