Test Server Feedback

lets see what I can do a bout a dev blog and some pink stuff karkur will write her own dev blog in blue

The Bastion Module was increased in volume significantly for (very good) balance reasons fairly recently. If you had one of those in your hold thatwould explain it.

Didn't have one of those in the hold. Just ammo, drones and some other items.

This would be good, something akin to the scan probe 'saved settings' option. I am constantly using specific setting mixed with more general ones. Ballache to get back to the specific ones.

It's very expensive to send information about everyone's health to everyone on the grid and is not something we could now easily do without a risking performance. The watchlist only had max 10 people until 2 or so years ago because of that.

Would it be possible to display that information in a column for ships either on watch list or locked? It wouldn't be for everything just the, theoretically, 22 ships (10 watch and 12 locked) that the user can already see.

Hoping that DScan may permeate into TQ soon, I elect to begin my post with quoting this truth I like, about coding in general:



That said, nothing really stops us forum creatures from constructively fantasizing, while CCP karkur is absent doing real work, and steeling herself against all feature creep.

So, I thought about how this could look, assignable tuples of range and angle, saved at least for the session, and - this I find important - super-unobtrusive in the scanning task flow ergonomics. To illustrate: a button with drop-down combo box would involve click-select-(scroll?)-click-clickscan. And that's only using a save, not even creating it! Not all that helpful.

What sprung to mind early was adding a fixed number of, say 4, buttons left of 'Scan', just a digit in a rectangle really, that'll work as follows:

• On click (clientsession-)memorize the currently set 2-tuple (range, angle) AND THEN execute scan.
• On click with no prior manual manipulation of range OR angle execute memorized scan; no saving anything, not even bother shifting the slider/textfields to memorized values.

Please let this sink, and now go through your usual scanning routines in your head with this addition. Finished? Ok.


One issue, obviously, is the detection of prior manual manipulation: I believe this feasible. But further there is a conflict with auto-executing scan after manual range-slider or angle change which we today very comfortably enjoy.

Since you are here (Rab See, Charlie Firpol, everyone really) and interested, I thought I'd ask your input. Any creative solution on how to bring your ideas to fruition? And/or on the above?

Oh, I dont want any of that saveable, dropdown menu thingy stuff.

Atm on the test server there is that totally awesome range slider, which has several ranges saved, like 0km, 1 AU, 5 AU etc.

All I want is PLEASE add one more option to that bar! 200 000 km!

This alone would basically cut the time I have to spend messing with the dscan in half in factional warfare.

Edit:

I thought it would maybe help to explain why this change is so importand for me. This is how scouting in factional warfare works most of the time.

- You jump into a system - maxrange 360 DSCAN
- You activate tracking camera, click on a complex (those are the things with acceleration gates)
- maxrange 5 degree DSCAN to see whats inside or at the complex
- scan all other complexes in 14 AU range
- warp to whatever complex has potential hostiles
- once you landed at the acceleration gate (and you´re not already engaged), short range 360 DSCAN.
Shortrange means, short enough that only whoever is inside that complex will be in your range. Usually the acceleration gate is 10 000km to 100 000km away from the warp-in beacon inside the complex.

The lowest pre-set range on sisi is atm 1 AU. That is too big! Often these compelxes spawn quite near to gates, stations etc and you really only want to see what is inside the complex, not what might be at a nearby gate or something.
So, without a smaller pre-set range, I would have to change the range manually to around 200 000km every time I want to scout a complex that is near to something.

Wow you just posted while I was editing my post oO Thank you a lot!

I really dont want to be picky here but ehm...exactly 100 000km is too close. Some complexes have a distance between acceleration gate and the warp-in beacon of exactly 100 000km, so this would get some wacky results once whoever is inside slowboats a couple of kilometers away from that beacon in the wrong direction.

1 mil km is very good, thank you a LOT again!