GSE: Sequences, Variables, Macros

GSE: Sequences, Variables, Macros

7M Downloads

[BUG] CREATING A SEQUENCE ( BY RENAMING AN ALREADY EXISTING ONE ) GIVES COMPILE ERROR.

lloskka opened this issue Β· 5 comments

commented

πŸ”΅ Describe the bug:

Hey Tim, found minor bug here .

It doesn't get in the way at all, and allows you to use all the functionality of gse.

When you create a sequence ( as title says, by renaming an existing one ), gives compile error ( it gets saved, but gives compile error )

πŸ”΅ To reproduce: (Steps to reproduce the behavior)

  1. Create or have a pair new sequences with these names for example ( fury_single & fury_aoe ) ---> important here having underscore bar in the name ---> _

  2. Mark any of these 2 new sequences created, and rename it just fury

  3. See error printed on chat ( compile error )

πŸ”΅ Screenshots:

WoWScrnShot_080824_181149

πŸ”΅ Expected behavior:

There may be a problem when renaming specifically with underscores and spaces ?!

πŸ”΅ GSE.lua file:

GSE.lua.txt

πŸ”΅ Desktop (please complete the following information):

  • OS: Windows 11 Pro 23H2 22631.3958

  • Game Version 11.0.0.55960

πŸ”΅ GSE Version:

commented

Oh boi, i have been soo wrong these past years?!

So nothing remotely similar in name to whats lets say active or in use.

So much stupidity not even remotely thinking meself THAT. 🀦

Ok! Have a wonderful day.

commented

You can’t call something just β€œfury” it’s too generic and thee are other things already called fury

commented

The bug here is you called it fury - what if came from
Or the _ is irrelevant. The solution to this is not to try to call this by common wow names like PVP or Arms or Frost etc

commented

It’s a super easy mistake to make and everyone has made it.

commented

If you called it DJ_Fury of DJ_Fury_ST you would have zero issue it’s only the super common names that other mods or terms blizzard would use.