Wootility + Wootomation... Some Changes Need Made

[pulsar berry]

This post is summarizing a # of discussion points made in the #💻│wootomation channel over the last several weeks.

1. We believe replying "it's an OS function" is not an acceptable response by the Wooting team to any feature requests, or complaints made by end users. The team should probe more to understand the underlying function/feature the user is looking for, and then determine if it's feasible to add it to the backlog of requests.
   1a) It's especially important to determine if the requested feature is readily available in competitor software.
   1b) Some examples are blocking alt+tab input, in addition to the windows key while gaming. This is a feature that's available in Razer, Corsair, Steelseries, and just about every "mainstream" keyboard brand's Windows OS software. Competitor feature availability should play into how Wooting prioritizes a feature's importance when adding it to the backlog.

2. Some basic Wootomation features need combined with the Wootility software. Specifically; the ability to add modifier keys when remapping binds. Wooting must consider what games/software their users utilize on a regular basis, and the # of binds those users might need to input. Valorant, and CS:GO players benefit from the 1:1 remapping Wootility already has, but MMORPG players, RTS players, and power users who use things like Visual Studio Code while gaming are left out.
   2a) Specific examples of binds Wootility needs to support are inputting more than 1 key at different levels of DKS, and Mod Tap. This would be an excellent start.
   2b) If you are a power user, please leave a comment below of specific examples for modifiers/multiple binds you'd like to see added to Wootility

Unrelated: I have a background in tech. I was a head of acct. management for a bay area tech co. before I became fully disabled. I am not impressed w/ the engagement I've seen Wooting employees have towards inquiries made about Wootomation -- However I am very impressed w/ how they respond to inquiries made regarding FPS games.

I'd like to see the team engage better w/ users who want to utilize this software for MMORPG's, RTS's, and other power-user types of activities.

[serene gazelle]

Just give us API access and allow us to hook a function for every key press. In python would be accessible.

For power users, this could be enough to do basically anything

Others can ask a GPT for help with python, its easy enough the ai should have no problem explaining it to them

[slender yew]

On-board memory macros please so we can use it on other computers with ease 🥺

Many premium/gaming keyboards have that feature so bit sad wooting doesnt have it

[wind shuttle]

Exactly! Wootings boards have so much potential but they're letting their competitors have a head start in front of them by overlooking this feature!

We appreciate your upvote 🙏

[slender yew]

Yeah, my skyloong sk61 had it too. I hated the software on that so would never run it other than to setup some FN macros. And they would work on my linux too

[wind shuttle]

skyloong macros before wooting macros is insane work lol

[robust root]

yeah I dont need fancy macros with coordinates like synapse, just some simple typing macros

[pulsar berry]

Agreed, and Synapse-like coordinate macros doesn't make sense... Because keyboards don't input mouse-like movements on the screen (coordinates). Keyboards do however require combinations of keys in different applications + games for certain inputs. Why this wasn't accounted for in Wootility I do not know.

If Wooting started selling mice, I'd expect them to account for coordinates in macros. But they don't currently.

Here's an example of something I tried to accomplish in a game I play, before I realized it's impossible w/ the Wootility software and had to resort to alternative binds altogether.

These are two different keybinds on an in-game action bar. The first is the "X" input. The second is "Ctrl" + "X". Both are configured to use similar, but different in-game inputs. Any hardcore MMORPG player might care about the difference. For the FFXIV fans reading this, the first is a ground-target shukuchi in-game macro, and the second is a target shukuchi macro using the in-game macro programming interface

When I first received my Wooting keyboard I tried to use Mod Tap to Instead make it so I could just Tap "X" to input the first key... but fully press "X" to input "Ctrl" + "X". This was until I discovered I could in no way input a modifier key ("Ctrl") + the original key using Wootilities current available functionality.

Now why, don't you ask, might I not just bind a different single key on the keyboard to replace ctrl+x instead? Well -- I would lose typing functionality in the game. I need to regularly communicate with other players using my full keyboard, input numbers on my numpad (it's why I bought the FULL wooting keyboard), and tab between other programs when I'm streaming/communicating with raid teams on third party platforms.

https://i.gyazo.com/f577de4e5130bd6b8cbe6867d16812d3.png

[pulsar berry]

In my opinion, this is a practical example of how Wooting can go a long way to bridge the gap for MMORPG players. A lot of us will have in-game macros built using tools Blizzard & Square Enix have already built-into their games. We just need our keyboards to have a little extra support on the software side to make use of the existing tools.

[polar cliff]

You can definitely use DKS to do X on tap and X + ctrl on full press. I don't think you can make it release X and then reactuate ctrl + X in that order on full press though, at the moment it'll just add Ctrl as a pressed key (producing X + Ctrl instead)

[stark void]

The main problem is my old keyboard Corsair K95 RGB and the Bloody S98 has features like onboard macro storage and continues repeating macro without any software needed. But there is no viable solution for wooting. Even for regular macros i have to use Wootomation and it's not enough.

Consider using onboard macro storage and activation of macros without any software needed. With that way we don't have to use any other keyboard as macro keyboard.

Also for the perfect combination;

• More than 5 macros should be stored in onboard memory.
• Between all the key presses, we should configure delay between milliseconds like 50ms to 100ms. Not constant 50ms or 100ms!
• You should have a option for continuous repeat just using onboard memory and chip.
• Software must be better. I suggest you guys to look Steelseries and Corsair iCUE macro section. But i want to mention best onboard repeating macro is at worst company on the list ''Bloody''. Their software is crap but the s98 keyboard has 100% onboard continuous repeating macro!

I just want to all of these extra ❤️

Please make wooting great again with proper macros! 🙏

[wind shuttle]

preach 🙏

[grizzled spindle]

I would love a continuous repeating macro too, I am forced to use a logitech mouse for that macro now but it would be ideal if wooting supports it too

[wind shuttle]

Wooting staff, don’t get me wrong—Wooting’s DKS feature is awesome. But it’s limited to just four actions, while macros let you get creative and run an unlimited sequence of actions with a single button.

[cosmic kayak]

Appreciate all the feedback gathered here and all the discussion in #💻│wootomation . Want to jump in to share about some Wootomation history, why it's not getting much love and where we want to take it.

The requests for macro's on Wooting keyboards is not new. Since the launch of the Wooting one (2017) we've been talking about how to approach macro's. For the first few years we always held off on development because we knew it was going to be a difficult project with a lot of side effects and specific requests.

We've always tried to focus on keeping things on board, simple, and use case specific. Examples of that are Mod Tap and Toggle Key. These are functions that a lot of people use and are simple to understand and setup. Firmware side it keeps the software development focussed and "simple" (it's still really complicated to balance all key processing parts, but that's a story for another time.)

Around 2 years ago there was an open window where two developers could combine their backend and frontend knowledge to develop what is now Wootomation. At that time we had a few goals in mind:

1. Keep it PC side to keep development "simple" and easier to offer features
2. Open source the software and open it for public development
3. Make Autohotkey simple to use. Try to reduce a complicated tool (macro's) into a simple setup
4. Cross OS
5. Hope it takes off as not just a tool for Wooting, but something that anybody can use

It took about half a year to develop Wootomation as it is now, plus some little updates in between. Some goals were reached, but some (painful) realities also unveiled:

1. Even if you open source your app, does not mean you get development help. Over these two years there have been 2 (!) external contributors.
2. Most use cases don’t utilise long sequences of characters, but are specific mixes of simple actions. You don’t need a full macro system for this.
3. The reality is that very few people really care about macro’s. I understand this can be controversial and makes it look like we care more about FPS gamers than MMO / RTS / Powerusers. This can be frustrating even for people that made Wootomation. Reviewers don’t mention it and most consumers just go with whatever’s default / the pro’s use.

So what does that mean for the future of Wootomation? It’s likely that we’ll keep on expanding on the “Advanced Keys” system and try to cover more and more specific use cases there in simple ways. Your FFXIV feedback @pulsar berry is a perfect example of where we can improve DKS / Advanced Keys or create a new Advanced Key to cover your use case. That gives you a great experience and us focussed development.

As for the Wootomation App it’s likely that it will go into a maintenance state where it can receive stability updates, but no new functionality.

I hope that gives some more insight into how we feel about this. I’ll keep an eye on this thread and want to highlight we closely follow all of this.

[pulsar berry]

ah, yes see the issue is I need the latter in order for DKS to be practical for me to use in any real MMORPG. (And I really, really want this to be supported. It'd be hella neat.)

here's an example of why I could never have a simple input of something like x on the up-input, and ctrl on the down input... these are all of my action bars, in FFXIV. Note: this is a relatively "light" amount of binds compared to WoW. (which I used to play more seriously some years ago).

Ctrl is a modifier for several different inputs (not shown). Alt and shift similarly used.

https://gyazo.com/3b07e07348cfc443f607aa29d3bf9bdc

[pulsar berry]

hey, you're founding a company . For what little it's worth -- I can understand the pain. Y-combinator '21 here back when I was working full-time. I think our CTO back then said "making a startup is harder than winning the lottery... more people fail than you ever hear about..."

wooting is doing a great job, all things considered. Keeping your ears to the ground and listening to users is the only way to continue to improve. Iterate, iterate, iterate etc.

If I can be of any assistance in providing insight into competitive MMORPG / RTS / poweruser use cases please feel free to reach out beyond this thread 🙏

[robust root]

yes, sometimes I need my fn+q to become press down shift + 1 2 3 4 5 6 / press up shift. this cannot be done with current dks or modtab 😦
or fn + z to be 1 + enter 'message' enter smth like these. maaaaaaaaaaybe in the future?

[wind shuttle]

Thank you for your response! Since Wootomation development remains a lower priority, I’d like to suggest a few improvements for DKS.

First, while DKS's preset tick rate options are decent, even the lowest setting (30) can sometimes be too high for certain games and applications. I discovered this issue when I first used DKS. My goal was to set up DKS to allow me to press and hold the "F" button to enter edit mode while also holding the left mouse button, allowing me to select the edit directly. This setup was meant to speed up editing by removing the need to click repeatedly. However, the problem is that, at times, the left-click actuation doesn't trigger because the tick rate is too high, particularly in Fortnite.
In another example, I use DKS with Call of Duty: Black Ops 6. I've set up DKS to walk at 0.1mm, run at 3.0mm, and initiate a tactical sprint when releasing at 3.0mm. However, sometimes the tactical sprint doesn't activate, which I suspect is also due to the tick rate being too high for the game.

My second suggestion, and I realize this might be a stretch, is to increase the number of available actuations with DKS and make the actuation points independent. Currently, DKS allows for only four actuations with one key switch, but I think adding two more would be helpful. Additionally, I believe customization would improve if each actuation point could be independent. Currently, the 1st and 4th actions, as well as the 2nd and 3rd, have linked actuation points. While this linking is convenient, having independent actuation points would allow for even greater flexibility.

Thanks in advance for any response you reply with or any consideration!

[floral cloud]

well the reason they are "linked" in that way is because they are just 2 actuation points not 4. its just that each actuation point has a press and release action

also for the tickrate thing id be surprised if both fortnite and bo6 cant handle inputs at the same rate their games run

the tickrate setting for dks is meant for mainly games which tie reading inputs to their FPS. this usually causes them to only read at a rate of 30 or 60 times a second. most newer games shouldnt have any issue with faster inputs at all.

[slender yew]

I think we should still have some more support for on board memory macros as it gets asked almost daily in the other channels

[drifting wraith]

at this price range, we can get competitors with the same performance and much better software

[wind shuttle]

yeah i was suprised as well but check it out!
https://youtu.be/4vcJnIAsErc

[wind shuttle]

would it be possible to get more actuations?

[serene gazelle]

Tbh if there was an API users would take care of the rest

[paper canyon]

Point 3. If your goal is to make the best keyboard to “challenge the (gaming) industry”, then the gap will soon close with your competitors that do allow complex macros. Personally, I’m a bit disappointed in this answer. I hope you guys also reconsider as someone who has spent almost 19+ years playing several MMOs throughout my life those features have been a god sent in middle of raids or pvp.

[wind shuttle]

i’m pretty disappointed too but i think their set on it, there’s no way we can get them to prioritize it i guess

[wind shuttle]

i couldnt send voice messages normally, so i had to send a voice file

[paper canyon]

Just vote with your wallet from now on I guess…

[floral cloud]

we disabled voice messages because people can just type

[wind shuttle]

Ahh i see, let me retype it

The DKS config I have set up is supposed to walk at 0.1mm of press down, run at 3.0mm of press down, and perform
a tactical sprint at a 3.0mm release up. The issue lies in that every time I try to use the tactical sprint
feature, it either starts the sprint but cancels within a couple of milliseconds or completely skips over the
sprint. However, I've found a workaround that makes the tactical sprint work around 90% of the time: by jiggling
the key up and down slightly around the 3.0mm actuation point. The entire purpose of this DKS config is to
alleviate stress on my pinky finger from holding down shift and to have all movement variations tied to a single
key. However, the workaround requires me to be consciously aware of it while playing, which can be challenging in
an FPS game where I need to focus on spotting enemies and getting eliminations.

I assume that it's a Tick Rate thing since i have 35 ping

[floral cloud]

i think for the cod case its also not tickrate related but a misconfiguration in dks

afaik you just supposed to double tap sprint key not hold it twice

(not to mention doing a hold like this twice will prob cause some issues with the engines input handling as it never gets a key up for the first sprint until you have the key fully released)

sadly dont have any of those games to try it

pretty sure an order more like this should work

[wind shuttle]

ill give it a try and let you know how it goes

[wind shuttle]

alrighty i can confirm this config does work and i thank you for that

Though what about the Fortnite config? As far as I can tell, there's no problem at least that I can see with its
setup.

The setup's purpose is to enter edit mode upon initial press-down (0.1mm) and use left click to select the edit
associated with the crosshair on screen, confirming the edit when the button is released after a 2.3mm
downpress.

[pulsar berry]

Fortnite is HEAVILY ping dependent fwiw, any pro can confirm. Inputs are entirely server side dependent.

(even 0 ping has a noticeable improvement over 30 ping, Epic's net code is terrible.)

[stark void]

@cosmic kayak I understood the current situation, my suggestion is please find talented people who work on development of onboard macros. Sometimes, We have to plug in our keyboards to another computer for work etc. All of this macro profiles must be on ONBOARD. Most of the company PC's don't allow us to install another software. This feature is really important for who works at IT etc. The keyboards of other company's are so bad for me. I just want to use wooting at gaming, at work, at friend's PC. Without onboard macros, it's not possible. Even my 10 year Corsair keyboard can do that. I don't want to compare two different companys but i'll happy to see wooting destroying them. ^^

[cosmic kayak]

I understand. I just want to be very careful in not overpromising something that I don't think we'll be able to implement on short notice. Can if you can share more specific use cases you use in your setup? How complex do you need your macros to be?

[cosmic kayak]

Agreed. Ideally we do everything on board, like we have done so far with keyboard settings and RGB. Implementing things on board while keeping input speed and memory usage under control is a lot more difficult, that's why we initially opted for PC side. Moving more specific use cases under Advanced Keys will be a nice in between here. Keep the development focussed and impact on runtime / memory minimal. But, again, we need (even) more feedback on specific use cases here.

[cosmic kayak]

Maybe we should have shareable DKS presets for these kind of cases

[fathom latch]

macros in wootility were promised even years ago, it can be seen on reddit posts made by wooting people, then they just decided to ignore everyone and forget about it.

Not having them while everyone is adding it to their new HE keyboards (pulsar, and corsair latest examples), from proprietary firmwares to VIA/QMK, it's awful to be fair.

[wind shuttle]

That sucks... Oh well, now i know thats not a wooting thing

[wind shuttle]

That would be convenient and a cool feature to have, so people don't have to copy entire profiles.

[stark void]

I think, you can make lights static single color for onboard profiles if person wants to add a demanding onboard macro profile etc. PC side makes it so much easier but also requires** "3rd party program"**. Even some games and programs don't allow to use 3rd party. I think 90% of wooting users actually gamers. I believe implementation of oboard profiles will change the people's mind. Most of my co-workers and friends think that wooting keyboards are good but only for gaming. In reality people don't have enough knowladge about magnetic switches. Wooting's only differrence is the magnetic, configurable switches. I think that there is no difference between keychron and wooting in terms of hardware.

I just want to say that, If Corsair or get magnetic switches... like K70 MAX. With their better software there is no need to use Wooting for me. That feels bad. Just consider onboard profiles. Without onboard profiles, Wooting doomed to declane it's popularity.** WE DON'T WANT THAT**. That's why we spend our time to give you guys feedback. Love you guys....

[fathom latch]

Years ago, I even was banned on PUBG for having on the system an autohotkey script to send to tray discord with alt+f4 instead of closing it, it was reverted at the end because they recognized it as a false positive and happened to a lot of people, but having those things running in the background instead of the keyboard is risky

[stark void]

Yes, previously i got a temp. ban at a game for just using CTRL+SHIFT+ESC Task manager combination lol. The support said don't use autohotkey because the game recognizes it as PvP macro WTF? Maybe some people use it for that but the buttons i use not related. 😄 After that i put an Excel macro for work. What happens is ..... i accidentally press it when i was trying to kill the boss. Anti-cheat kicked me instantly.

Even the buttons are not related to in game attack or defense skills. I got auto-kick etc. We have a lot of exaples like this. That's why i stop using wooting that much.

In my use case, There is NO advantage of Wooting if you have Corsair K70 MAX keyboard with magnetic switches. Because of onboard memory and macros. I have no problems with it. Very cheap alternative is Bloody S90 regular red switches. Their software UI is so bad. That's the only keyboard allows 100% onboard continuous repeatable macro profile.

I check feedback section everyday. LET'S MAKE WOOTING GREAT AGAIN guys!

[wind shuttle]

I agree—Wootomation shouldn’t be left in the shadows. It deserves active development, with the goal of bringing it forward as a polished, stable, and fully public feature!

[pulsar berry]

Hi, I'm back to drop a comment. I'm having an issue, which I believe would be resolved by a feature. This issue has been occuring for some time (but I was thinking I was crazy for a while). Now I've actually discovered what the problem is, and how to reproduce it. I have not had this issue w/ my previous keyboards. It seems to be an issue w/ keypress priority/memory? I'm unsure what the "term" would be for a software solution that would resolve this.

During this short clip, focus on the two buttons I have highlighted in the accompanying screenshot. The top one is activated by pressing Alt+1, and the bottom is just the "1" key: https://gyazo.com/ec937161b34f93c5440c3a03fb1b92cf

I am holding down the alt key at all times during this short video clip: https://i.gyazo.com/d05fc899799f7ab3ddce4d2a14e70047.mp4

I am pressing Alt+1 repeatedly. This is what I want to do, as a user. while I do this, I occasionally tap the "Tab" key. This is intended. Whenever I tap the "Tab" key, the "Alt" keys input is 'forgotten' by wooting, and the system appears to only input 1.

You can try to repro this yourself in any input tester, I believe?

Once again, I'm unsure how this would be fixed w/ software. All I know is it's not an issue w/ competitor software I've used in the past.

(For the knowledgeable mmorpg fans; I'm spamming an ability that I have bound to alt+1. Note that I also have an ability bound to 1. However, as with most MMORPG players I happen to have my "swap target" keybind to tab. (this is default for most mmo games, unless changed). So when one target dies I hit tab to find another. Hitting tab cancels out alt, for some reason, swapping my input to just the spell I have bound to 1. Very sad :<

while not impossible to work around, it requires remembering to pause all inputs to swap target. This can result in some downtime depending on the game/context. for the mega-sweaty like myself, it's disappointing.)

[hallow aspen]

When you enter an edit and select almost at the same time, Fn will ignore the select edit input entirely. I don’t know if this was done deliberately or if it’s a byproduct of your system latency. Either way, you can learn to play with it, as did I, by shortly “hovering” the key or using a tactile switch (the tactile bump makes hovering the key easier). This is something you’d need to do anyway in order to edit stairs. If all that is too much, the only solution Wooting could implement in order to bridge the system and/or server latency gap is a minimum delay. It would allow you to set a minimum delay between DKS’ first and second actuation. For example: (with a minimum delay of 15ms) If you press your DKS key and the time between the first (Mouse 4) and second (Mouse L) actuation is 5ms, it’d delay the second (Mouse L) actuation by 10ms to make the minimum delay between the first and second actuation 15ms.
I suggested this before but it’s so niche that I don’t have much hope in this ever being implemented.

[hallow aspen]

On the contrary, selecting in editing hasn’t been server sided since season 3 of the first chapter IIRC.

[stark void]

Any update about onboard profiles? @cosmic kayak

[stark void]

I don't know but i feel bad. 😦

[stark void]

Still no updates?

@cosmic kayak

[hidden solstice]

I know it’s somewhat important for some people and I would like it too, but multiple pinging of Wooting staff is not the way to go. If there is an update then someone would post it.

[dapper canyon]

Wooting has the best software. some might have more features but wooting is easy to use, looks good, web based, and it just works. you dont need to look something up, or watch a youtube tutorial, or anything.

[drifting wraith]

I was talking about wootomation, wootility is great.

In my opinion, they should be combined, but wootomation, atleast the last time I used it, was very flawed

[hidden solstice]

And it still is

[last hemlock]

agreed I think that if combined it might also create more awareness and interest in the wootomation side of things

[stark void]

Until they decide to take this seriously, i will not give up. Even if they don't come with that update. I'll make a youtube video about it to show the problems and why people who want specific macros shouldn't buy woothing. I try to do my best, hope and wait the update....

[haughty bear]

im sure they will.
let em rest a bit post xmas, they did say theyre gonna have vacation time away from work.

soon all will be patched up n improved

[stark void]

Yeah, I like the team a lot.

I hope they'll bring the update.

[hidden solstice]

Wootomation will not receive feature updates, it was written somewhere, so don’t expect much for that project.
What could happen at some point is hardware based macros or more advanced functions like dks.
And I hope that they don’t integrate the current state of Wootomation into Wootility as it would decrease the quality of it.

[frank finch]

Hello, sorry if this was asked already many times, but I tried to figure it out myself and by searching this discord and google but still not sure if I understand it right... Well. Is there any way to save a macro directly to the wooting keyboard? So it works without having wootomation running in the background? I had some keys on my old coolermaster Keyboard remapped, for example to switch between windows desktops and also other stuff. And i am using this on my working PC also and cant install wootomation there. It's actually a core feature i am looking for in a keyboard and cant believe wooting doesnt support this, since almost any higher priced keyboard does?! thanks in advance!

[hidden solstice]

No it’s not possible, no way to save or run macros from the keyboard itself. (Only the actions in advanced keys)

[frank finch]

God damn it. Thx for your answer. If i knew that before i wouldnt have bought it tbh. Guess I have to think about returning or not then 😕

[floral cloud]

soon™️

we do wanna do more with the advanced keys but rn theres just other focal points

[frank finch]

So you are actually planning on implementing this? Also for "random" keystrokes, which the user can define himself?

[pure lichen]

😑

[frank finch]

okay tbh that doesnt mean anything. But i get it. It's stressing that the same question is coming over and over again. But the problem is, since it came so often and there are different answers (also on different plattforms), it's really hard to figure out, whats true or not, if you are new to the topic. So sorry guys for bothering you, but also thank you for your help.

[hidden solstice]

#1301320998209196052 message second last section

[barren pawn]

The "Fn" key is on a different position...

[hidden solstice]

This is totally the wrong place for it and you already asked in other channels.

[hallow aspen]

Soon™ means anywhere between now and the heat death of the universe, FYI.

[frank finch]

TBH i also dont really know, what to do now. I just got another keyboard of one of the competitors and it delivers full macro support safed on the device and all other features as well. Just the RGB and the sound is a little worse, on the other hand the layout is a little better imo. But also i have to say, that i already fell in love with the wooting a little bit and its just this one feature, that is missing. I'm just wondering, since I think this cant be that big of a deal and maybe there was just a minor request for it, as long as the main selling keyboard was the 60HE, which was mainly used for gaming. But i guess releasing the 80HE will bring more customers like me, who dont only use the keyboard for gaming but also for office work and maybe the request for on board macros is getting bigger. I'm really torn back and forth between what to do. Guess i gotta sleep a night over and also check return policy on a already built 80HE module, case and so on.

[hallow aspen]

At this point in time, there’s isn’t a board that can do it all. They all have strengths and weaknesses which you have to consider when trying to pick the right board for you. Although I’d love on-board macros on Woot’s boards, I don’t care much for them as the software based alternatives are fine to me. I think the feature set and switch compatibility is the most important to look for in a HE board, both of which Woot does really well. Different people look for different things of course. If you want to get rid of your 80HE, I would try to sell it rather than returning it as you might get more for it. ;)

[frank finch]

You're surely right about that. None of em does it all. I just gotta weigh up the pros and cons to me. Dunno yet.

[pulsar berry]

If your team at any point needs beta tester(s) for software changes, I'd love to help. Still keeping a keen eye on discord, and other channels for any mention of changes come down the pipeline.

[floral cloud]

all our betas are public

https://beta.wootility.io

[dapper canyon]

yeah everyone tests the betas

[pliant rose]

Hello @pulsar berry, I hope you're doing well. I wanted to kindly ask if there are any updates regarding the repeat while holding feature.

[pulsar berry]

Hi, I haven't seen any updates yet myself. I need to install the beta

[stark void]

@cosmic kayak Hi everyone, i have an update. Madlions released MAD68 Pro and MAD68 HE. These keybaords has similar software like our Wootings but! They have onboard macro feature. Everything except onboard macro feature looks same as Wooting. It means that the onboard macro capabilities can be achieved.

[floral cloud]

no one said it cant be achieved

[stark void]

Really waiting for it ^^

[pulsar berry]

I think we'd like some more context than this? I understand you've expressed in the past that the "main" concern internally has been esports, organizers, maybe having separate firmwares for esports/everyday users... Is this still the primary blocker (coming to a conclusion on how to best address this concern as a company)? Or is it a developer bandwith problem? Or something else?

[pliant rose]

Could you kindly share when you plan to add the "repeat while holding" feature? Apologies for my lack of knowledge on this, but I’m curious to understand why it’s challenging to implement, especially since many lower-end keyboards offer this feature by default.

[stark void]

I said same thing at the begining.....

[stark void]

I demand some answers too. But my conclusion is I think they don't have enough experienced programmers for this etc.

[stark void]

Any news?

[stark void]

@floral cloud @cosmic kayak Sorry for bothering you guys but i feel really bad as a Wooting lover. Please, give us some information.

[pliant rose]

I don’t think we have any chance with this, and it seems like no one here is willing to listen to us.

[grizzled spindle]

Sad :(

[stark void]

@floral cloud @cosmic kayak Any updates?

[hallow aspen]

We’ll have to wait till the 60HE v2 drops. Then we’ll see more software development until they start to work on another new board.. 🥀

[hallow aspen]

or maybe not? #📣│announcements message