Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: MapTool 1.12.0 Function getState always return 0 #3642

Closed
Predictabowl opened this issue Sep 19, 2022 · 5 comments
Closed

[Bug]: MapTool 1.12.0 Function getState always return 0 #3642

Predictabowl opened this issue Sep 19, 2022 · 5 comments
Assignees
Labels
bug tested This issue has been QA tested by someone other than the developer.

Comments

@Predictabowl
Copy link

Describe the Bug

As per subject the function "getState" always return 0 regardless of the actual value of the state on MapTool 1.12.0
It worked fine in 1.11.5.
I've only tried on Linux so far.

Anyone else experiencing this?

To Reproduce

On a new campaign drop a single token, impersonate it and set the "Dead" state.

In the chat type [r: getState("Dead")]
It will return 0

Expected Behaviour

It should return 1.

Screenshots

No response

MapTool Info

Version: 1.12.0

Desktop

Linux Mint 21

Additional Context

No response

@Phergus
Copy link
Contributor

Phergus commented Sep 19, 2022

Confirmed.

@Pmofmalasia
Copy link

It seems like there might be pervasive issues with functions related to states and potentially bars since 1.12.0 alpha, given issues #3558 and #3514 - unsure if there's others I've missed.

@Phergus
Copy link
Contributor

Phergus commented Sep 20, 2022

Additional note that this also affected the direct use of states such as [r: state.Dead].

@Jmr3366
Copy link
Contributor

Jmr3366 commented Oct 1, 2022

I've not able to duplicate this with the built-in states using indirect and direct means. I believe this can be closed.

@Predictabowl
Copy link
Author

Seems resolved in 1.12.1, should I close it or wait for the owner?

@Phergus Phergus closed this as completed Oct 1, 2022
@Phergus Phergus added the tested This issue has been QA tested by someone other than the developer. label Oct 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug tested This issue has been QA tested by someone other than the developer.
Projects
None yet
Development

No branches or pull requests

4 participants