Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×
Create a free account

Default grid color is broken

Selecting colors in campaign settings (at least for black) causes it to make the default color in rgb format instead of a hex code, making the grid invisible
I get this problem with the Tokens as well! I'm trying to default to hex code #ffaf00 & #ff0000 for my Auras, but it instead defaulted to rgb() which the VTT doesn't recognize!
Doesn't happen to my auras. I'm using updated chrome on windows 10.
1519994503
Ziechael
Forum Champion
Sheet Author
API Scripter
Thanks for flagging this, and sorry for the slow response... I'll flag this for further investigation.
Hi everyone! A bug ticket has been submitted, and the devs have a good idea on where the issue is coming into play :) Fix should be coming as soon as we can!
While we're at it, when selecting grid colors in campaign settings there's no way to input a hex code, can only select the default colors. Is that intentional?
Moonman said: Doesn't happen to my auras. I'm using updated chrome on windows 10. it's only if you change the Default Aura Color in the Campaign Settings, the original Default is in the correct format, but once you change off of the original Default, there's no returning it to that format, it switches it to things like rgb(255, 0, 0) instead of #ff0000 which is what it recognizes in-game for Token Auras. the Original Default uses # whilst every single other default uses rgb() and even the #transparent uses rgba(0, 0, 0, 0)
in case anyone was curious about the status of this bug, it's still there, the formatting is still incorrect (as I mentioned in my previous post a week ago)
Drespar said: Hi everyone! A bug ticket has been submitted, and the devs have a good idea on where the issue is coming into play :) Fix should be coming as soon as we can! As soon as you can doesn't seem to be particularly soon does it?
Moonman said: Drespar said: Hi everyone! A bug ticket has been submitted, and the devs have a good idea on where the issue is coming into play :) Fix should be coming as soon as we can! As soon as you can doesn't seem to be particularly soon does it? I concur! I also have been spotting these Arrows in the Background sometimes when I'm editing my Tables, and the Arrows allow me to add Columns & Rows correctly, although they're not in the foreground, nor are they in the Handout's Window (they seem to be offset around -500 -100 from the location of the Cell). I mean, this is quite simple stuff really, I could probably learn how to code it myself and create the patch before this seems to actually get fixed. This is why GitHub Source Code is such a useful thing, because if you have an error, anyone can just come strolling along and patch it right up for you, but as this is a Site which has a Premium Membership Feature, I'm assuming that it's a White-Listed GitHub Access probably exclusively for Pro Members (Premium+, Free++) unless the people really know what they're doing. The problem with this being that only the people who actually manage to keep a Pro Subscription can actually do any of the Heavy Lifting for the Dev Team. If the Dev Team can actually just bring those Arrows to the Foreground, and correct the Offset of them, and make it so they show up for all of the Tables instead of just randomly, that'd at least hotpatch the Table issue, and allow them to work their magic for 2 min on the correction of the Defaults to Hex Code instead of HTML Code (seriously, it's a simple Ctrl + F in the Source Code, I don't see how hard it is, it's 1 menu. You even have everything you need to find and fix it, we would do it, but we don't have access)
Still not fixed.
This Thread is 2 Months Old!