[hazard]

The possibility to filter varp changes in the Dev Toolkit, or to detect changes from within the script. As it's quite a mess atm to inspect the varp you need; over 10 can change at a second.

 

[slashnhax]

Support, it would be nice. Even something as simple as a checkbox for each varp to listen/ignore would be sweet

 

[hazard]

It shouldn't be that hard as the dev toolbox is already listening for varp changes..

 

[arbiter]

I approve. @Cloud

 

[cloud]

The possibility to filter varp changes in the Dev Toolkit, or to detect changes from within the script. As it's quite a mess atm to inspect the varp you need; over 10 can change at a second.

How do you propose that a filter would be implemented in the dev toolkit?

 

[hazard]

Just the possibility to ignore certain varps or to listen for changes would be nice too

 

[slashnhax]

@Cloud will this be implemented or should I make a tool do do so?

 

[aidden]

How do you propose that a filter would be implemented in the dev toolkit?

The way I'd picture it is you double click a varp and it gets listened for. When we're listening for one or more varps, no other varp changes are shown in the live changes box. Then you'd just need a way of indicating which varps are currently being listened for and a button to stop listening to all and maybe double click the varp again to remove individual varp from the listener

 

[slashnhax]

The way I'd picture it is you double click a varp and it gets listened for. When we're listening for one or more varps, no other varp changes are shown in the live changes box. Then you'd just need a way of indicating which varps are currently being listened for and a button to stop listening to all and maybe double click the varp again to remove individual varp from the listener

Personally I just envisioned it as another column, with checkboxes denoting listening/not listening.

 

[aidden]

It might also be a nice idea to have a collapsable list of previous values rather than just the last value