bump until this is fixed.
AGS hates PVP players so this will likely never get fixed. They made a vague allusion to “it’s hard to code into our engine” some time ago which makes it even funnier. Funnier and sadder.
Yeap how hard could it be to colour a border around the active aoe/healing circle with just red color = enemy & green/blue = team
bump until this is fixed.
bump
Its only 2022, we dont have advanced enough technology to make enemy abilities a different color, its a very complicated highly advanced thing and AGS is a small company with a very low budget so we should be understanding that it will probably take atleast 6 more years for them to be able to make something a different color.
bump until this is fixed.
bump until this is fixed.
bump until this is fixed.
I’m no game developer but I’ve worked with unreal engine and unity. I’ve made countless of textures for various 3d models and games.
There is NO EXCUSE for this still not being in the game 1 year after release.
You already have the groundwork for the coding which determines the dye on armor for red and blue.
Apply it to spell effects already.
Ice shower either gives haste buff or gets u stuck and dead.
Playing frogger hopping between 14 different sacred grounds in combat trying to find one that heals you is not acceptable.
There is no excuse in this world which is valid for this STILL not being fixed.
bump until this is fixed.
bump until this is fixed.
Way overdue a fix on this. Ice as well as heals.
Yeah Ice wall is the worst. I have and IG on my team, and I see an icewall so I walk into it, not knowing it was an enemy that had an IG that I didn’t see. definitely sucks
Tone down the particle effect as well. It is like a cloak of invisibility in big battles. Can’t see who you are fighting at all.
and still a pain in the ass to find your group members. Can we get blue health bars or something for group members? It’s really stupid this is still an issue. Finding group members in war is such a pain.
bump until this is fixed.
bump until this is fixed.
up , we really need this ![]()
bump until this is fixed.