Timestamps are in GMT/BST.
| 01:38:47 | | BFDiscordBridge Quit (Remote host closed the connection) |
| 01:38:47 | | BFDiscordBridge3 has joined |
| 01:39:41 | | BFDiscordBridge3 is now known as BFDiscordBridge |
| 06:14:36 | | BFDiscordBridge Quit (Ping timeout: 258 seconds) |
| 06:47:40 | | BFDiscordBridge has joined |
| 07:21:46 | | BFDiscordBridge Quit (Ping timeout: 256 seconds) |
| 07:31:11 | | BFDiscordBridge has joined |
| 08:33:10 | | BFLogBot Repo: bitfighter | Commit: 196502d6d6 | Author: raptor | Message: Use static_cast |
| 08:33:11 | | BFLogBot Repo: bitfighter | Commit: 2fb5363db2 | Author: raptor | Message: Remove TODO in comment |
| 08:33:13 | | BFLogBot Repo: bitfighter | Commit: 99da94805f | Author: raptor | Message: Remove (hopefully) unneeded line |
| 15:58:59 | BFDiscordBridge | <πΉβ£πΉπ»πΈπ»πβ‘π> Why would this render method be calling a BFObject, rather than a ForceField child? |
| 15:58:59 | BFDiscordBridge | <πΉβ£πΉπ»πΈπ»πβ‘π> https://cdn.discordapp.com/attachments/325743140059480065/720774108979134484/unknown.png |
| 16:36:50 | BFDiscordBridge | <πΉβ£πΉπ»πΈπ»πβ‘π> okay figured it out its because forcefield is a different kind of object from forcefieldProjector |
| 17:08:46 | BFDiscordBridge | <πΉβ£πΉπ»πΈπ»πβ‘π> Alright so fading the forcefield projector to show health looks really dorky |
| 17:11:02 | BFDiscordBridge | <πΉβ£πΉπ»πΈπ»πβ‘π> Looks like we'll have to do a healthbar type option |
| 17:11:02 | BFDiscordBridge | <πΉβ£πΉπ»πΈπ»πβ‘π> https://cdn.discordapp.com/attachments/325743140059480065/720792236530466883/unknown.png |
| 17:11:33 | BFDiscordBridge | <πΉβ£πΉπ»πΈπ»πβ‘π> possibly I could make the beam dynamically fade but that's a lot of work and idk if it'd look better |
| 17:16:17 | BFDiscordBridge | <Skybax> Force field health seems unnecessary |
| 17:19:02 | BFDiscordBridge | <πΉβ£πΉπ»πΈπ»πβ‘π> Its a big quality of life improvement, to be able to see how much progress you've made damaging it or how much healing it needs, just gotta find how to do it |
| 17:28:53 | BFDiscordBridge | <Skybax> What if it's solid and becomes empty |
| 17:29:43 | BFDiscordBridge | <amgine> make it thinner based on its health? |
| 17:30:11 | BFDiscordBridge | <amgine> or maybe make the base triangle filled and empy empy as it t akes damage? |
| 17:30:20 | BFDiscordBridge | <Skybax> That's what I just said |
| 17:30:48 | BFDiscordBridge | <raptor> change the duty cycle on the FF border |
| 17:31:49 | BFDiscordBridge | <Skybax> what |
| 17:32:27 | BFDiscordBridge | <raptor> the bright border can be said to have a duty cycle of 100 % |
| 17:33:18 | BFDiscordBridge | <raptor> change the border to be a progressively smaller duty-cycled dashed line: https://d32zx1or0t1x0y.cloudfront.net/2011/06/atmega168a_pwm_02_lrg.jpg |
| 17:33:49 | BFDiscordBridge | <Skybax> So basically make it more jagged? |
| 17:33:53 | BFDiscordBridge | <Skybax> Like the emitter is faltering |
| 17:33:57 | BFDiscordBridge | <raptor> correct |
| 17:35:40 | BFDiscordBridge | <Skybax> That would be cool but I'm not sure it would be noticeable |
| 17:36:07 | BFDiscordBridge | <raptor> yeah we'd have to just try it and see |
| 17:36:30 | BFDiscordBridge | <amgine> so you could make it start to be dashed as started or could you have the width of the barrier decrease as it gets weaker? |
| 17:36:52 | BFDiscordBridge | <Skybax> It's already not wide |
| 17:40:09 | BFDiscordBridge | <πΉβ£πΉπ»πΈπ»πβ‘π> Is duty circle something that's already used? I haven't seen that term in code |
| 17:41:35 | BFDiscordBridge | <raptor> cycle |
| 17:41:39 | BFDiscordBridge | <raptor> no |
| 21:26:30 | BFDiscordBridge | <amgine> rip circle items you shall be missed |
