[BUG] Cant save option to Bliz character macro
djazzington opened this issue · 7 comments
🔵 Describe the bug:
I was able to save the new gse to the global character macro but not to the character specific one. It was locked into the older verson of the macro and would NOT delete
🔵 To reproduce: (Steps to reproduce the behavior)
- create new keybind with new gse system
- open macro menu click on Character specific. Old gse macro still there. delete
- create new macro in character specific old GSE Macro returns, delete
- go to general macro create save it works on general but it will NOT go onto the character specific side
🔵 The error:
It pastes my OLD gse sequence when on character specific macro
🔵 Expected behavior:
I expect it to put in the NEW sequence not delete and restore old
🔵 GSE.lua file:
🔵 Desktop (please complete the following information):
- OS: [e.g. Windows 11 64bit]
- Game Version [retail 11.0.0)]
🔵 GSE Version:
- Version: [e.g. 3.x.y] 3.2.01-8
- Downloaded From:. https://www.curseforge.com
🔵 Additional context:
Add any other context about the problem here.
have a test import
d8J5iaGAvvRhIxsvXHjsETc1TrPzsLZHIzdsESQsUjPonL4Bke1LPK2jc7LQSBr2VQs9tQknmv53QittszOqYGbPmCfshKsDufchtrhxf1cf1sviYIbA5s5Hq5Pq1YuQNdPMijtvLAYePMUGlQKRsv1ZuvCDaBuiBvLSzeTDk(ii(QKQpdQVlXijQXseJwQgpHtcs1zvW1q68OALc1ALKrPc7n9U9WhvkouNKsAVBp8lPAwKcekRO9U9cE4AP(QDcT3ThoK(j0HVHw9tqr(n0wPUujpCWAg2vZjc0c)2OfbLv7RuxDaUnxs0ihGLMF5c3pDcetcRCQDEWricGeIaIGJBeilka7GLyrOjqQ1ieH0aMVmB1JzNXBc760o)a1dQyYn2J25D5DUQrebrnZ4i6OXmdC5uxDaUbQ70yOAerqugo(ToAmdAvLrhbr5dMJew9HboRPD(OMUkMCJ9udyhGBauQInoTZ)YaNFuc0RKXoMrNxua2kU0SuGyrGrZhHzZFnZQUrlctGZs)pdRgHyb6HJho1yrhAwgB1dhSMHD1CIaTWVnArirQU(f5QgbgQ7cYkn5YnbcbJgJsNa1PtGnjCEA0ItKXSZAtGNbE9OtGy2U9LQRUyGZphm2b4g4XOXUtD1GBB7OeOVol4dQcYZOZUzzDaUl(zGTL)fz1njIJegrrjqFXw4vTpyosHYr3ChTZZ0DowUW9tli4oDMy6IG8lqQmWkMZc(GQG8ODoSKc)2OJGKiTVsBB8ADUFtpJtjqFXw4vnIii3U8vc2wMQZojfB)QI4aCd8y0y3PUAWTTDuc0RKXoMrNxua2klvSsohlcmA(imB(Rzw1nArycCw6)zy1ielqpC8rT0Seksb1yRTVHgKMuE4G1mSRMteOf(Trlcjsmu)c7NsWXVlid0oV)l4R0Kl3eiemAmkDcuNob2KW5PrlorgZ(QnbEg41JobIz72xQU6Ibo)CWyhGBG6ongQ2hLSKTT7)ZFfTZ7)cESrhnM5lL8)hextG43uYuANNP7SVKAS75S4JPW9z6IgZmWLtDvLPGnn6CSrhb52LVsW2YuD2jPy7xvehGAmxsG8MsRK))G4AerqqSMLNfKdWnGVmB(ijb6rqOffUeD0yMbUCQRoa3f)mBUVK6SFdCgfDJOODEauyp4GvFiHZJKrJrWsebr5dMCQGCGYhrWT5xuT4ezf77S0S1RnbU(12UeScW1XC0jqI8DgnJpIh1j8WLT2ozbnRhoynd7Q5ebAHFB0IGmaYatXUAQfHuH)mBKRFXALiXwjNswsr5OUGelvSRePYj3vR00sL8o)P9jFjbwHcKicImaYatXUAQJgZmWLtD1bOU5(fCCANhaf2doy1bQhuXKBShTZTy0yxUn2nLa9kzSJz05ffGTYsfRe2yrGrZhHzZFnZQUrlctGZs)pdRgHyb6HBJo0KcQVHgE3czWdhSMHD1CIaTWVnArG8H9(fCCANhKl26gHiKk8NzJC9lwRej2k5uYskkh1fKyjWUsKkNCxTstlvY78N2N8LeyfkqIiiKpS3VGJt78GCXw3iIgZmWLtDvLPGnn6CSrhb5xGuzGvmwQshGWODKWzu0nYb4g49lqKN6iiTz(zkz8ADoyQRgiHZhGBaFDAKNeOhbHwu4s0rJzg4YPU6aSC2FQGu1iWKLOJGOauOAfU)ub5a1dQyYn2J25zqRy4KLL7xioa3nuiWQdWDwt78NCb5auhKj1ytkb6l2cVQreb5M8CDjfo1OXu0o3IPWXD6mbTZdgcmcJoAmdAvLrhbr5dMJew9HboRPD(OMUkMCJ9udyhGBauQInoTZ)YaNFuc0RKXoMrNxuGufKqAdelcmA(imB(Rzw1nArycCw6)zy1ielqpCNf4Eizjb)n0YNGk4HdwZWUAorGw43gTiibWMqgw53PZe0o)lg48JobIjHvo1op4iebqcrarWXncKffGDGnweAcKAncrinG5lZw9y2z8MWUoLa9fBxDbk4VMGhFRJgZmWLtD1biCaLc2(rl2(v6ii)VmEJiAmDcGkTZ(PUGe24u9ZsFALMzOJQGe36gkOazLmbWKpaJsjvlkPhUS12jlOz)gAlOSYAnfKYdhSMHD1CIaTWVnArqgazGPyxn1rqmwZUzbXFtWxPjxUjqiy0yu6eOoDcSjHZtJwCImMDO2e4zGxp6eiMTBFP6Qlg48ZbJDacJ29)jJkjYhOEqftUXE0ohKU5UuxnqcNpa3TPdgrMU5okb6l2cVQrebrgazGPyxn1rJPtauPD2p1fKWgZwzTIDLMzOJQGe36gkOazLmbWKpaJsjvlkPxWdFbLvwRPa2jGuWJyK9WXTEgWA6lRO9U9cEbp8aFuRE4y(6ClSBO7lHxWZd
That on a shaman is doing all sorts of weird things
I’m not sure why that’s doing the - the down side is I can’t look at it for 36 hours. I’m away from the computer on a training course. I’m sorry I can’t address this sooner.
Issue is I cannot seem to make this happen. I follow the instructions and it just doesn't do it for me. I am assuming that by macro you mean a /macro macro not a GSE Sequence.
Are you getting GSE to manage the macro through the Macro button on the GSE Menu?
@djazzington Could I get you to EA_BMH_OB in the GSE Macros part and turn off managing this macro? I wonder if this is the cause
I have added an attempt to fix this via 3.2.02-f-1 If anyone could test and let me know how it is behaving