Funky [6:59 PM]
@svara I am quite sure the EULA is against any accelerated input meaning round robins and the like.

Because in isboxer you can set a keymap that rebinds your mousewheel to round robin inputs to client, since you can scroll the mousewheel so quickly it is indifferent from broadcasting however it is still 1 button = 1 action ingame.

Funky [7:14 PM]
"However, if any third party application or other software is used to gain any unfair advantage, or for purposes beyond its intended use, or if the application or other software violates other parts of the EULA, we may fully enforce our rights to prohibit such use, including player bans.

We do consider overlays using elements of a second or multiple other EVE clients to be against the rules. It changes the way the game is played and grants the player unfair advantages over other players. For example, having overviews from other EVE clients as overlays on one EVE client would allow a player to get real time intel from all those other game instances without having to switch to the other windows."
I honestly consider Near2 to go against this as it can use a background clients information to overlay information onto a main client. That would be the same as a VFX feed of the intel chat onto your main client.
Even if in a roundabout way.

Naidin Iwaira [7:20 PM]
for what do you need multiple instances of eve using near2?

Funky [7:22 PM]
If it can overlay information from a background client then yes.

Naidin Iwaira [7:22 PM]
I think you dont know how near2 works x)

Funky [7:23 PM]
Can I use VFX feeds to make a dashboard of intel channels from multiple clients on a dxnothing window? Gains no advantage to someone using log scraping.

Naidin Iwaira [7:23 PM]
Near2 allows you to track only one char at a time

Funky [7:24 PM]
Even if that character is a background client?

Naidin Iwaira [7:25 PM]
So your construction would be you are a neut in nullsec traveling and having a spy char in their intel chat?

Funky [7:26 PM]
Near2 you can set multiple listeners

Naidin Iwaira [7:30 PM]
There is still this option:
https://cdn.discordapp.com/attachments/458635059885375489/470160523481055232/unknown.png
https://cdn.discordapp.com/attachments/458635059885375489/470160523481055232/unknown.png

and you still rely on that someone other is posting sth.

Funky [7:33 PM]
That is the map that is displayed, not what clients are actually listening right?
VFX feeds of chat  channels would also do the same thing, others would still have to post it

Naidin Iwaira [7:36 PM]
I understand the rule in the top more like you have one client open and have like x local chats/overviews displayed.
which is a `real time` display
chat is no `real time`? (edited)

Wibla [7:38 PM]
NEAR2 depends on players actually posting intel in a channel
it's not a fully automated thing

Funky [7:38 PM]
So does vfx feeds of other clients channels
For example, having overviews from other EVE clients as overlays on one EVE client would allow a player to get real time intel from all those other game instances without having to switch to the other windows.

This kinda explain Near2s intent

Wibla [7:38 PM]
iirc splitting up windows and shit is not allowed?
though I may be wrong
what you could do is have 4 scouts in various systems and stagger the windows... then stream that whole monitor on twitch :vv:

Funky [7:39 PM]
It isn't because you can get information about background clients into a easy to see map of information
Kinda like background chats into an easy to see map of information

Naidin Iwaira [7:40 PM]
there is still a human in between

Funky [7:40 PM]
Yes, there is still a human using the VFX dashboards

Naidin Iwaira [7:40 PM]
no there is still a human playing in that system else near is useless
and therefore is a delay
delay <> real time

Funky [7:41 PM]
The point was it overlays background client information on top of the foreground client
Which has been the argument against VFX feeds in the past

Naidin Iwaira [7:41 PM]
and the human could also report something wrong whereas a remap of all overviews would give you a 100% accurate thing
`real time intel`<<< the reason why i would say near2 is legal in my pov

Funky [7:43 PM]
Doesn't matter if it is a human in the chat or a bot. The information is from a background window right?

Wibla [7:43 PM]
people are _really_ bad at reporting accurate intel

Naidin Iwaira [7:43 PM]
the bot is illegal
since it relays realtime intel

Wibla [7:44 PM]
NEAR2 parses a chatlog file

Funky [7:44 PM]
Chat is still realtime intel even if someone is reporting slowly

Wibla [7:44 PM]
"realtime intel" :v

Naidin Iwaira [7:44 PM]
you have a wrong definition of real time

Funky [7:44 PM]
Does it get the chat information as soon as it is in channel?
Or does it get a delayed chat?

Naidin Iwaira [7:45 PM]
delayed since it still waits that the client wrote the log file

Funky [7:45 PM]
Ok fine, I will set a delay on my vfx dashboard and should be ok :thumbsup:

Naidin Iwaira [7:45 PM]
or more accurate it needs to wait till the drive wrote the file

Funky [7:46 PM]
no more accurate than the time the vfx dashboard is drawn