Feels like every time I do anything, something strange happens with my parties of the "am I just losing my mind?" variety. I've been having the weirdest week with this game. What of every effects do you prefer the most? There are more effects from evergreen and event champions else, but leveling up the evergreen champions is cheaper than the event ones, so I have frequently seen Cattie Brie (& Zorbu) and Krull (& Paultin) in campaigns but contributing with low percentages of 'Assault Party Damage' and 'received Scales of Tiamat'.Īt this point, I question if in campaigns where Jarlaxle and Makos are chosen I should contribute with another effects like 'Increase all Champion Damage', 'Reduce all Damage Received', 'Reduce Base Attack Cooldowns' or 'Reduce Ultimate Cooldowns', instead of low percentages of 'Assault Party Damage' and 'received Scales of Tiamat'.
Ironically, the most used champions are Jarlaxle and Makos, evergreen champions whose benefits are, respectively, both described behind. # If someone presses CTRL+C, close the JamHat, freeing of the Pins for use elsewhere.The more reasonable ones I had frequently seen so far are 'Assault Party Damage' and 'received Scales of Tiamat', which are very useful because the first one helps players finish the campaign thrice (as maximum) and the second doubles (as maximum) the received amount of scales. # each looper needs to go until 300 ( which is equal to 30 minutes )Ĭalc_number_lights_to_switch_on(jamhat, loopcounter, selectedTimer) If(jamhat.button_1.is_pressed): # blue button # Setup infinite loop in try / catch so user can CTRL+C terminate (if and only if keyboard attached) if you wanted a 5minute timer = 60 * 5 = 300 / 6 = 50 # 30 minutes timer 60 seconds * 30mins = 1800 seconds / 6 (each loop takes 6 seconds ) = 300
Turn_off_all_lights_and_turn_on_green_lights_to_indicate_ready(jamhat) # Turn the green lights on (indciates booted and program ready) Sleep(6) # keeps the loop count timer the same (so all calculations should work on timting )ĭef turn_off_all_lights_and_turn_on_green_lights_to_indicate_ready(jamhat): # loop array based on numberOfLedsToLightĮval(lights) # call eval on each element in the array, up to the count e.g. Print("numberOfLedsToLight = "+str(numberOfLedsToLight)) TurnOnThisManyLights(jamhat, numberOfLightsToLightNow)ĭef turnOnThisManyLights(jamhat, numberOfLedsToLight): NumberOfLightsToLightNow = math.ceil(numberOfLightsToLightNow) NumberOfLightsToLightNow = float(loopcounter) / float(gapForEachLight) GapForEachLight = float(selectedTimer) / float(totalNumLeds) # do the calculation to work out how many lights to turn on #ĭef calc_number_lights_to_switch_on(jamhat, loopcounter, selectedTimer ): # gpiozero contains the JamHat object (the little circuit board with the lights and buzzer on it) The & in the script above runs the program in the background so other functionality is not affected on startup (ie it doesn’t halt anything as its spawns a child process). I’ve started the script in an infinite loop (via crontab), so it functions standalone on start up (no need to trigger anything, other than starting it via the blue button on the Jamhat board).
Idle champions of the forgotten realms formations code#
Its functionality is all in the code python below. When 30 minutes is completed a tune plays (well a couple of beeps, sounds very 8-bit ). The lights come on at equal times in the cycle so after 15 minutes there are 3 of the 6 lights lit. When you click the blue button, that starts the timer (its set to 30 minutes by default, but this can be altered by changing the timer variable ).
I use it as a Pomodoro Timer for timing 30 minute intervals. This is a timer for the Raspberry Pi that lights the lights on the JamHat Hobby Board as the timer progresses through its cycle.
0 kommentar(er)
