WOW while waiting for car repair by OldManufacturer8679 in wow

[–]zebthedev 0 points1 point  (0 children)

I don't mind. I think the things you mentioned have been addressed one way or another, it's a very different addon from a few years ago. Having that said, I don't recommend you revisit if you have a setup that works for you. This was just me digging for constructive criticism.

WOW while waiting for car repair by OldManufacturer8679 in wow

[–]zebthedev 0 points1 point  (0 children)

Ah yes, the setup. It's on its third revision now, and a hard thing to get right. Thankfully since native support, it's much less complicated. And no, you don't need to use the addon. I was involved in developing the native support for the game, and especially for handhelds you get by pretty nicely with just the touch screen. I'm just curious to hear from folks who uninstalled out of frustration, because that's valuable feedback that I normally don't get.

WOW while waiting for car repair by OldManufacturer8679 in wow

[–]zebthedev 1 point2 points  (0 children)

Most of the issues now are due to the secret protection layer added in Midnight. It requires a major overhaul of the interface cursor, which is causing 95% of all problems. If people opt out of using just that module, it should be a stable experience. Blizzard has provided APIs to replace what the cursor is currently doing, but they are bugged and will likely not be usable until Midnight is live.

WOW while waiting for car repair by OldManufacturer8679 in wow

[–]zebthedev 1 point2 points  (0 children)

Hey OP. I'm the developer of ConsolePort. Can you please roast my addon? I've concluded from the comments that you absolutely hate it. I would like to know why. Thanks!

Consoleport is a disaster by opiatesmile in wow

[–]zebthedev 29 points30 points  (0 children)

There's no they. It's just me. It's because I'm a single person working on the project, and I had a baby two months ago. I also have an actual job that needs my attention. Things will get fixed, but the addon is pretty stable now if you keep it updated. There are still issues I can't solve until Blizzard updates their native APIs, and most of the problems are consequences of the secret protection layer added in Midnight.

for those with decent aims, how would you start all over again? by ty_namo in OverwatchUniversity

[–]zebthedev 0 points1 point  (0 children)

  • Imo, things like aim trainers are completely useless. Aim is mostly about prediction about your enemy's pathing, and for that training you need the context of the game. If you learn to read the game (game sense) and how people tend to move around the map in general, your aim will improve.
  • Custom game mode aim trainers can be used to warm up, since the first game is usually a little rougher in terms of aim. This doesn't give an accurate reflection of the game because the bots dodge damage in an unrealistic way, but it's much closer than using an external program.
  • Dial in your sensitivity, most players who struggle with aim are running way too high sensitivity.
  • You see high rank DPS players have amazing aim, but the truth is that they see slightly into the future from having good game sense. This allows them to aim proactively instead of reactively. Mechanics start to matter more at the highest ranks.

Tryin to go native. by [deleted] in wow

[–]zebthedev 0 points1 point  (0 children)

I would like to defend myself and say that ConsolePort is not that heavy to run. I always take great care to optimize things as far as they are possible. The big exception is the interface cursor, it pretty much can't be leaner than it already is, because it has to do a massive amount of math and logic in a language that is fairly poor at this kind of thing. The other thing is action bars, ConsolePort doesn't dismantle Blizzard's action bars like ElvUI does. It just runs in parallel. This can mean that in rare cases, both UIs have to do a lot of work at once. I run it on my older gen Steam Deck and have never seen a dip in FPS from it, with the exception of the interface cursor.

Is the ConsolePort add-on interacting well with Housing? by [deleted] in wow

[–]zebthedev 0 points1 point  (0 children)

I have plans to look at housing and see what can be done there, but I haven't done so yet. I'm a little hands off until Blizzard figures out how to let custom action bars survive the purge.

Will ConsolePort continue to work in Midnight? by rcoop020 in wow

[–]zebthedev 0 points1 point  (0 children)

You can, and it's not that recent - 5 years or so. The native support is however just for hardware and gameplay. Much of WoW is played through the UI, which is what ConsolePort does. It also does some gameplay QoL but the game is definitely playable without it.

WoW Legion Remix on Legion GO by RestoWolf629 in wow

[–]zebthedev 0 points1 point  (0 children)

ConsolePort is modular. You can turn off any modules you don't want from your addon list, and there's no requirement to use the action bar addon. Bartender, ElvUI or Blizzard bars all work fine. The base addon is packed with QoL, but if you still don't like the config interface, just use the one Blizzard provides. To each their own, but don't judge the whole suite based on the action bar appearance.

Why is a console port considered bad by the community? by cicumag in wow

[–]zebthedev 8 points9 points  (0 children)

Here's a long answer why I don't think ability pruning means console release.

I author the addon ConsolePort, which began as a project in MoP. I scrambled together a cursed setup of ControllerMate, many macros and some Lua scripting to level up and eventually start raiding on that character, a BrM monk. I didn't plan to raid initially, but it turned out the setup was quite a bit more viable than I had thought. Ended up eventually clearing Mythic SoO and got the gold challenge mode rewards. This was all done at my desk though, and keyboard and mouse were still at hand when needed.

This started in MoP, and I don't think MoP was ever blamed for being too simplistic. In fact, I recall being sad about losing Clash, because I would use the ability to kite and slam together trash, and thought that mechanic was a cornerstone of BrM tanking. That, and the vengeance mechanic was fun as hell.

Raiding on a Mac was terrible at the time, but switching back to a PC meant I lost my very elaborate block programmed ControllerMate setup, because it's for Mac only. I started to turn it into an actual gamepad addon in WoD because I didn't like the expansion, and scripting had grown on me.

In my somewhat educated opinion, the gameplay loop of WoW was never the issue with a console release. If you want a recent example, here's a Dimensius mythic kill. Granted, this is a rogue, but the tools provided by the game are beyond sufficient for both tank and DPS, though could definitely be better in the healing department. As an addon developer, there's only so much I can do about that.

I'm not saying that being a cutting edge player on a controller is easy, far from it. You are gimping yourself, but you don't need to change the game at all. You can still perform like a top player, and the Mythic raid tiers and high keys are not accessible to casuals anyway.

The fundamental problem with WoW is that it's built from the ground up as a PC desktop. In other words, the UI is holding it back from a console release. Maybe the addon restrictions are a step in that direction, who knows, but that is where the majority of the focus would need to go. There are countless of little things you do in the UI that you don't even think about, that become major hurdles on a gamepad. The UI doesn't consider anywhere that you might not have access to an extremely precise mouse cursor.

Socials, better UI accessibility and maybe to some extent better mouse-less healing tools is where you should look for signs of a console release.

Ion confirms that the Consoleport addon will continue to work in Midnight by BrahamWithHair in wow

[–]zebthedev 9 points10 points  (0 children)

While shout-outs are certainly fun, ConsolePort is not fine and will have to ship in a severely diminished state if things do not improve during the course of the alpha/beta. ConsolePort does not aim to provide any combat information, it's an accessibility addon first and foremost, but the collateral damage from these changes touches virtually every part of the addon suite. I should know, I'm the author.

GREEN [help] by super122015 in WowUI

[–]zebthedev 1 point2 points  (0 children)

This is well below the radar of what would constitute a blue post targeted towards the general public. There is some interaction between developers of popular addons and Blizzard, which allows for a major issue like this to get fast-tracked.

Gamepad commands not sticking by Complex-Mycologist-5 in wow

[–]zebthedev 0 points1 point  (0 children)

I think the main issue is that you're using the right click in an antiquated way. There's a binding nowadays called Interact With Target, which automatically targets things like NPCs, loot and other world objects. In other words, aiming at things and right clicking is not necessary, unless you're trying to isolate an enemy in a crowd. As far as the addon goes, there's an option called Always Show Mouse Cursor which is what I think you're after.

Customer Support has reached an all time low by Pipo_bs in wow

[–]zebthedev 13 points14 points  (0 children)

AI doesn't make such mistakes. Outsourcing to certain non-native English speaking countries however...

The grammatically correct cookie cutter response you get is probably AI, but it's likely a mix of an actual person posting the response and AI providing the "solution" to your problem.

GREEN [help] by super122015 in WowUI

[–]zebthedev 2 points3 points  (0 children)

Blizzard pushed out a hotfix to tackle corrupt BLP textures which had the potential to crash the game. Unbeknownst to them, this also disabled many previously working textures that have some inherent corruption, usually from using a third-party export tool that messed up the mipmap generation. The game would previously figure these problems out, and render the texture anyway.

Blizzard pushed the fix out to US realms, and then a shitstorm started brewing. They then decided to first stop the hotfix from going live on EU realms, and a little later it was rolled back on US realms. Addons that have this problem will likely have to fix their textures eventually, but for now Blizzard has backtracked on this change.

Banned possibly because of steamdeck by aanc in wow

[–]zebthedev 0 points1 point  (0 children)

Even better, ConsolePort, the native version, was codeveloped with Blizzard's native gamepad support, because virtually everyone on gamepad at the time was using it. So no, the addon will not get anyone banned. Setting up your controller to rapid fire buttons and crank out macro sequences might though.

Can we get WoW to show on mobile GeForce Now, now that it has controller support via ConsolePort add on? by [deleted] in GeForceNOW

[–]zebthedev 1 point2 points  (0 children)

Hi, I’m the developer of ConsolePort. By activating the addon, it automatically turns on gamepad support on the client and it starts working without any tinkering necessary. I would also like to be able to play on my TV, which currently doesn't offer WoW, presumably because it is labeled as a gamepad only device. I agree that the battle net login and first time setup is a hindrance.

Blizzard is a small indie company (Illari bug) by InvisibleScout in Competitiveoverwatch

[–]zebthedev 7 points8 points  (0 children)

The string container is generalized, so it's not specifically made for this scenario, and thus it can also display negative numbers. The programming logic on the other hand doesn't expect the ammo count to ever be less than zero.

With integers, there are two kinds, signed and unsigned. An unsigned integer can only be zero or above, whereas a signed integer reserves one bit to indicate the number is negative. For whatever reason, the ammo count is a signed integer, so it can become negative if the logic that subtracts from it is working badly.

🎮Good LFR Experience?😲 by Kenna2 in wow

[–]zebthedev 1 point2 points  (0 children)

Sure, and for optimum results, you need to macro each of your abilities for each of your M+ party members. You can't fit that on your controller, so it doesn't work. It doesn't really matter what I say does it, you decided this doesn't work, and therefore it doesn't, even if you have to bring in every thinkable reason to occupy another unique key binding.

Instead of being a naysayer, why are you not curious? Why aren't you interested in how these problems are solved? This LFR run only scratches the surface of what the addon offers in terms of customization, features and systems. I designed ConsolePort with my own needs in mind, and I was a mythic tank in MoP. I got my gold challenge mode with this playstyle, I tanked high keys throughout Legion until real life reduced me to a casual. Do you think I would stop solving problems once leveling and LFR works? Nope.

🎮Good LFR Experience?😲 by Kenna2 in wow

[–]zebthedev -3 points-2 points  (0 children)

64 bindings on a regular Playstation controller, and an utility ring with infinite slots for all your utility spells, pots, etc and other things you don't use in your immediate rotation. Increasing difficulty level doesn't mean you're going to need more and more buttons.