Clicking on Hide Areas TWICE (and every other-time after that) causes areas to be revealed. Clicking on Reveal Areas a second time, (and every other-time) causes areas to be hidden. This bug has been around for 5-7 weeks or longer and I
keep hoping it is fixed each time I run a game. I run two different
games each week. (one uses dynamic lighting, but I disabled most of it
(Saltmarsh), and the other.. and this is the important part... the other
game never had Dynamic Lighting. AND this same bug occurs in both games. Here's why it is terrible for my games. Please provide a solution: 1. I'm running the game. I'm revealing areas, hiding areas, and reading the scenarios, writing whispers, talking, and more. 2. Then, I need to hide an area to make sure it actually is hidden, so I click on "hide area", draw a big box, and suddenly a large section of map is REVEALED to the players. THIS IS BAD. Why is it bad? A. It wastes my time constantly checking a corner of the map to see if my "Hide Areas" is going to "hide" or "reveal" this time. B. If I skip "A" then players see something they are not supposed to see. C. It distracts and takes my focus off the game, and onto the tools, and makes me curse Roll20 for not fixing this after 6-7 weeks. D. It makes me want my money back from my pro account, because this used to work before the new Dynamic Lighting broken everything. Please fix one or two lines of code in the javascript. Please? I beg you. Please fix one line of code. I's just one line of code. I can even fix it for you. Here is the fix in pseudo-code for the two buttons. Instead of doing this: revealAreasBoolean = !revealAreasBoolean; Please do this instead: Reveal areas If (revealAreasBoolean == false) { revealAreasBoolean= true; } Hide Areas code If (hideAreasBoolean == false) { hideAreasBoolean = true; } The code-behind is flipping the boolean state in the javascript or code, rather than checking the state first, then setting it. flipping bits without checking what they should be set to is a weak coding practice going back at least 20-25 years, but weak coding practices are still taught in the colleges. I can imagine the college teacher saying "Hey, do this cool thing, because it is short, clear, concise," because college teachers probably aren't very good at this thing called "Good-Coding practices." (I was one, so this reflects on me too! Life is about learning and getting better... Anyway...) Also, Please don't suggest that I use Updated Dynamic Lighting because it is slow, fails constantly, and requires constantly going back and forth between maps and opening doors that are too small to click with a mouse, (and it is basically a punch in the DM and players collective faces - It's a really great idea to make Roll20 like a videogame, but the implementation leaves MUCH to be desired. I mean seriously, I player can move 30 feet max, and the players drag their tokens all over the 150 cavern.) Anyway. Thank you. Thank you. Please fix this bug. Thank you. Please fix it. It's like 2 lines of code. Please Thank you. Thank you. Much appreciation. Thank you. Please fix two lines of code. It's been like 2 months now. Please? Thank you. For the love of all things sacred, please fix this bug. Seriously. I'll do anything to get you to fix this bug. Just ask. Do you want me to go stomp on 50 baby ducks? Because I'll go find 50 baby ducks and squish them like overripe oranges. kidding. joking. I love animals. I actually do. If you have read this far, then please fix this bug. Thank you.
