- Keyboard Shortcuts by JosephStar318 · Pull Request #30 · bisterix-studio/parley

JosephStar318 · 2025-09-18T20:55:11Z

No description provided.

jonnydgreen

Thanks for submitting! Great work so far! I've done a first pass and left some comments :)

One general comment is that upon an execution of an operation, we need to update the underlying AST and clear up any open editors in the dock. As you mentioned on the linked issue, this means we need to notify the main_panel that something has happened. The implementation for this probably depends on the outcome of some of my comments - happy to help when these are sorted/agreed :)

Some thoughts for the future:

Testing this will be interesting - if it's not easily possible, no problem at all but it will be interesting to see what we can do with GUT!
We'll need to think about adding some documentation as well. Nothing major, just something to say what keyboard commands are available etc. Again, happy to show you how the docs work when the time comes :)

Any questions, give me a shout!

jonnydgreen · 2025-09-25T16:58:51Z

Apologies for the delay - very busy week! I have time this weekend and tomorrow afternoon to have a further play with it :)

JosephStar318 · 2025-09-26T11:14:57Z

Apologies for the delay - very busy week! I have time this weekend and tomorrow afternoon to have a further play with it :)

No worries, i couldn't find time to continue my work on this anyways. Maybe this weekend i will get some stuff done

JosephStar318 · 2025-09-27T13:05:52Z

so here is a question, I managed to delete a node successfully and save the dialogue ast. But undoing it will require for me to re-add the node to the dialogue ast and I couldn't find a capable method for doing that. only method i found is
add_ast_node which expects a dictionary. I wanted to be able to give the node of type ParleyGraphNode or maybe its id, and change the dialogue ast. How can I do that?

…s, undo delete WIP

jonnydgreen · 2025-09-28T10:43:30Z

No worries, i couldn't find time to continue my work on this anyways. Maybe this weekend i will get some stuff done

Thanks and absolutely no rush on your end as well :)

jonnydgreen · 2025-09-28T10:57:43Z

I wanted to be able to give the node of type ParleyGraphNode or maybe its id, and change the dialogue ast. How can I do that?

Good question! add_ast_node is probably not what we want as this is for use by the importer - I'll make a note to document this as I'll admit, it isn't clear :) How are you currently storing deleted nodes? I think we may want to store the AST (e.g. ParleyMatchNodeAst) in the history!

If storing as an AST, I would recommend defining a new method that accepts NodeAst as an input, given that different nodes store different data. This would then add it to the DialogueSequenceAst. So something like:

func add_node_from_ast(node_ast: ParleyNodeAst, insertion_index: int) -> ParleyNodeAst:
  # Probably need to make sure the provided ID doesn't already exist
  # Also worth storing the insertion index somewhere as well?
  nodes.insert(insertion_index, node_ast)
  _emit_dialogue_updated()
  return node_ast

wdyt?

JosephStar318 · 2025-09-28T11:12:04Z

I wanted to be able to give the node of type ParleyGraphNode or maybe its id, and change the dialogue ast. How can I do that?

Good question! add_ast_node is probably not what we want as this is for use by the importer - I'll make a note to document this as I'll admit, it isn't clear :) How are you currently storing deleted nodes? I think we may want to store the AST (e.g. ParleyMatchNodeAst) in the history!

If storing as an AST, I would recommend defining a new method that accepts NodeAst as an input, given that different nodes store different data. This would then add it to the DialogueSequenceAst. So something like:
func add_node_from_ast(node_ast: ParleyNodeAst, insertion_index: int) -> ParleyNodeAst:
  # Probably need to make sure the provided ID doesn't already exist
  # Also worth storing the insertion index somewhere as well?
  nodes.insert(insertion_index, node_ast)
  _emit_dialogue_updated()
  return node_ast
wdyt?

i was going to store the nodes itself without queuefree them. but storing asts makes much more sense. Only problem is that i don't have access to the ast from the parleygraphnode itself. if there was a variable inside maybe i could do that. or let me know if there is a way to get ast from graphnode.

jonnydgreen · 2025-09-28T11:34:01Z

Very good point - we don't currently store the AST data within the graph nodes themselves.

We do have the ID and we have access to the Dialogue Sequence AST in parley_graph_view which we could use to grab the (node/edge) AST data and then store a .duplicate(true) of this in the history. I think this could work even with deletions, although I haven't verified this - wdyt? The alternative is to move the history logic up a layer into the main_panel and trigger from emitted signals from the graph view and mutate down from main_panel (this is something we may wanna do anyway in the future)

One other thing I've just thought of that we may need to consider is: providing dialogue sequence context to the history. For example, what if we?

made some changes in Dialogue Sequence 1
switched to Dialogue Sequence 2
undo those changes

wdyt?

JosephStar318 · 2025-09-28T11:48:31Z

Okay i will use the id to get the ast. But to make things loosely coupled I prefer handling the operations inside the operation. If we need some components or scripts we can insert them when creating the operation.
The current undo redo history is stored in the main_panel.gd. so my question here would be does main_panel reset when you load a new dialog? If it resets we don't need to do anything it will just clear the history as well. but if it doesn't change like you said we need to group by dialog sequence. it should not be a big deal, just going to make a dictionary of history.

jonnydgreen · 2025-10-03T09:35:33Z

things loosely coupled I prefer handling the operations inside the operation

Agreed - nice one!

so my question here would be does main_panel reset when you load a new dialog

I believe it would as it should call the refresh method so as you mention, it should be okay - one for us to double check! :)

JosephStar318 · 2025-10-05T10:42:28Z

func add_node_from_ast(node_ast: ParleyNodeAst, insertion_index: int) -> ParleyNodeAst:
  # Probably need to make sure the provided ID doesn't already exist
  # Also worth storing the insertion index somewhere as well?
  nodes.insert(insertion_index, node_ast)
  _emit_dialogue_updated()
  return node_ast

Does insertion_index matter? Couldn't we just append the node_ast? As i understand, the nodes array in dialogue_sequence_ast.gd are handled with like push_back functions which doesn't care the index.

jonnydgreen · 2025-10-12T12:41:07Z

Does insertion_index matter? Couldn't we just append the node_ast? As i understand, the nodes array in dialogue_sequence_ast.gd are handled with like push_back functions which doesn't care the index.

Good question! Atm the nodes array is in order of node creation, so I was thinking that if you delete a node in the middle of an array and then undo this deletion, it's gonna cause some unexpected git diffs in the output dialogue sequence JSON (.ds) file because the re-added node would be in a different position in the file. It's not the end of the world, and certainly a nice to have, because as you point out, it doesn't affect functionality - I don't have a strong opinion either way on this! :)

In the future, we could probably add some kind of ordering to the nodes array in the JSON output but that's probs out of scope for this PR! On a side note, I also want to spend some time looking into using dictionaries under the hood as this will be keep performance good at scale

JosephStar318 · 2025-10-12T16:32:41Z

okay then, for now ill just append the nodes for now. It might be better to sort them later because if a bulk deletion is requested it will be very hard to manage the indexes of multiple nodes at the same time

jonnydgreen · 2025-10-13T09:10:57Z

okay then, for now ill just append the nodes for now

Sounds good to me!

- undo redo history grouped by dialoge sequence ast

JosephStar318 · 2025-10-18T10:35:22Z

I have finally finished the delete operation and undo redo functionalities are working smoothly. even between two different dialogue sequence. Needed to add some get or find methods to get access to ast's. Let me know your feedbacks

jonnydgreen · 2025-10-26T11:50:44Z

I have finally finished the delete operation and undo redo functionalities are working smoothly. even between two different dialogue sequence. Needed to add some get or find methods to get access to ast's. Let me know your feedbacks

Awesome stuff! I will have a look asap

jonnydgreen

Hi! Really good progress! :) Just reviewed the code now and left some comments - let me know what you think!

I also had a play with your changes just now as well and I couldn't get the redo/undo to work (delete is fine) - I got the following errors in the console while playing around with: all.ds - have you come across these errors?

I also noticed a slight bit of colour weirdness when creating a new edge, every out going connection turns blue instead of staying light green. I don't know if you've noticed this?

Just FYI, I'm starting a new job next week so I may be slow to respond over the next week but I will have some time on weekends :)

jonnydgreen · 2025-10-26T12:24:39Z

+			elif key_event.keycode == KEY_DELETE:
+				delete_selected.emit()
+
+func _handle_mouse_select(mouse_event: InputEventMouseButton) -> void:


Just looking at this function logic in detail, it seems a little quadratic. I wonder how this will behave for large dialogue sequences - especially since it's running on every left click event, which is a very common operation.

As a result, I suspect we may have performance issues with this, so to be on the safe side, I'm thinking that maybe connection selection is a feature we could maybe turn off in project settings and allow users to opt-in?

wdyt?

maybe if we cached the connections it would be better. i haven't experienced a performance issue, all though i don't have a low-end computer to test it.
Selecting and searching through connections can be simplified with an id but i would have to generate id for each connection. ideally it would have been nice to integrate this with the parley_edge_ast since that has also generated id but that is a task that would require a lot of time to finish at least for me.

cool, if you haven't noticed a performance issue so far then that's good news - I've got a few large Dialogue Sequences so I'll see how they fair - I'll report back :)

ideally it would have been nice to integrate this with the parley_edge_ast
Agreed, something for the future for sure!

jonnydgreen · 2025-10-26T12:32:59Z

+var previousToColor: Color
+var selected: bool
+
+func _init(_edge_ast: ParleyEdgeAst, _from_node: ParleyGraphNode, _from_port: int, _to_node: ParleyGraphNode, _to_port: int) -> void:


Nit: in _init methods, I think it's generally good practice to add a default value to the parameters so you can in theory call it as follows: ParleyGraphEdge.new() - I can't recall where I read this, but I think I read it in the gdscript tutorial

i do think it could be misleading. if someone forgets to put parameters it will still compile but will give errors on runtime since the parameters are expected to have a value

i do think it could be misleading.

See the docs comment here, this is the thing I remember reading: https://docs.godotengine.org/en/stable/classes/class_object.html#class-object-private-method-init

So if we were to call duplicate on this class, it would fail. I think in this case, I generally prefer to use factory methods for this. I do take your point on it being misleading however.

So, if we're only ever instantiating this directly then all good! But maybe worth adding a comment to illustrate this just in case :)

Alright I'll add a comment

JosephStar318 · 2025-10-26T16:59:29Z

Hi! Really good progress! :) Just reviewed the code now and left some comments - let me know what you think!

I also had a play with your changes just now as well and I couldn't get the redo/undo to work (delete is fine) - I got the following errors in the console while playing around with: all.ds - have you come across these errors?

I also noticed a slight bit of colour weirdness when creating a new edge, every out going connection turns blue instead of staying light green. I don't know if you've noticed this?
Just FYI, I'm starting a new job next week so I may be slow to respond over the next week but I will have some time on weekends :)

i just realized you could also set the color of ports. i think i changed the slot color and that is why it affects every edge.

I will take look at the errors probably going to need a lot more testing.

The undo redo didn't work assuming you were on a mac and based on the other comments you wrote there is no support for it right?

jonnydgreen · 2025-11-02T16:16:00Z

i just realized you could also set the color of ports. i think i changed the slot color and that is why it affects every edge.

I see! Can we fix this behaviour so it doesn't change the colour of related edges when creating new edges using click and drag? Cheers and as always, lemme know if I can help!

I will take look at the errors probably going to need a lot more testing.

Cool cool! Lemme know if you need me to test anything specific :)

The undo redo didn't work assuming you were on a mac and based on the other comments you wrote there is no support for it right?

I think based on your code it should be supported provided I used ctrl+z but it seemed to be erroring for me - but I could be wrong! Give me a shout when Cmd+z (etc) support is added for Mac and I can re-test :) In the meantime, I'll dig into why this is happening as well since I can replicate the error

jonnydgreen · 2025-11-09T11:33:24Z

Just FYI, I'm almost done with translation support here - I don't think there are any conflicts with your PR but I thought I would mention incase you wanted to have a look :) #28

JosephStar318 · 2025-11-16T14:22:26Z

sorry for the delay i was super busy these couple of weeks.

as for the progress, i implemented the macos support and learned that port color doesn't exist. it's a default behavior by godot to change all the connections one side color when you set the slot color. there might be an advanced solution which i am not aware of. Would like to see if you encounter any more errors after this last commit.

Co-authored-by: Jonny Green <me+github@jonnydgreen.com>

JosephStar318 · 2026-02-07T18:03:49Z

I have done your suggested changes. also i have committed and improved edge selection with bezier calculation. And i didn't imagine it would work this smoothly, you will see the result yourself :D
Then i added node creation undo redo support as well as duplicate with cmd/ctrl +d. that is also supported with undo redo.
Probably tomorrow i will take a look at the copy and paste. It should be easy but need to offset the nodes to the cursor position somehow. Its getting real close to its final shape though.

jonnydgreen · 2026-02-10T19:24:54Z

cool! Taking a look now! :)

jonnydgreen

Great stuff and outstanding work with the bezier curve! As you say, we are getting there! 🚀 (And of course, no rush on the copy/paste work!)

I haven't finished my review yet as I've mainly focussed on the duplication operator this evening - I'll continue this over the weekend as I'm busy every other evening this week unfortunately!

In the meantime, I had a play and it's working nicely at first glance:) I did notice the following issues, I don't know if you've come across them?

Duplication nodes don't copy values
Weirdness happens with the edges when I do the following on all.ds:
a. Duplicate node 27
b. Add edge from 27 -> 29
c. Undo change
d. ==> Weirdness with edges
Duplicating with multiple selections didn't work for me

- changed name connection to edge - removed some of the commented code - added copy function to nodeast - improved duplicate operation - added copy paste support

JosephStar318 · 2026-02-22T10:31:37Z

done your suggested changes and added copy paste support! please take a look

jonnydgreen · 2026-02-23T20:39:01Z

done your suggested changes and added copy paste support! please take a look

Fantastic! :) I will take a look this week and answer all your other Q's!

jonnydgreen

Hello! Happy March! :) This is soooo good! I've been having a load of fun with it today! We are very close now!

Thanks for implementing the copy/paste functionality, I've just tried it out now! 🚀 On the whole it's working great! I've had a few intermittent issues with it unfortunately and am unable to create edges on copied nodes. Here are my steps to reproduce, lemme know what you think:

Copy node or duplicate node
Try and connect an edge to it

I believe the issue is with the use of duplicate and references. Having looked in depth at this, I think we will need to adjust to a more reliable approach as follows (this also gets rid of some of the other issues I was seeing):

I'm also seeing a few other intermittent issues crop up here and there which are hard to reproduce - (mainly when testing the undo/redo functionality and playing around with edges). Given this and the best kind of testing is using this for real, I think we should put this behind a feature flag in the Parley settings as an opt-in feature (I'm gonna do this with my translations support PR as well). With this in place, this will allow us to release this very soon and once we are fully confident, we can switch to on by default! :)

As I mentioned in my previous comment on this, this can be done in: parley_settings.gd and constants.gd (if you agree, I recommend: "parley/editor/keyboard_shortcuts") but lemme know if you need a hand or guidance with this

As I understand it, we have the following left to do:

Fix any remaining bugs/implementation details
Tidy up code, and remove/fix any prints/todos
Fix any GDScript warnings/errors
Put this behind a feature flag and set to opt-in (add a TODO to switch this to opt-out)
Testing - after which, I can do a final bit of review polish
Documentation (can be done in a follow-up PR - I'm happy to do this if you'd prefer)

Anything I've missed for what is left to do? :)

I'll aim to spend Thursday/Friday evening of this week doing some further testing this feature and get us ready for merging - really, really well done!! And thank you so much! 🚀

jonnydgreen · 2026-03-01T20:50:46Z

+		id = new_id
+	elif not id or id == id_prefix or not id.begins_with(id_prefix):
 		id = new_id if new_id.begins_with(id_prefix) else "%s%s" % [id_prefix, new_id]
-#endregion


I think this may have been accidental, could we revert this please - thanks :)

this was needed because i couldn't override an id to a newly created instance of node_ast via .duplicate call. If you have a better workaround i will gladly accept it.

copy function is not needed anymore and removed but setting the id externally still requires this change, i believe on of your comments you made a suggestion of changing comment on the id setter so i take it this is resolved

ah sorry - I was referring to the deletion of the #endregion only - the other changes are all good :)

jonnydgreen · 2026-03-01T21:26:26Z

 	if arrange:
 		arrange_nodes()
+
+	call_deferred("refresh_edges")


Is this addition needed? It's unfortunately conflicting with some of the existing refreshing functionality (e.g. unexpected nodes get reselected after clicking the refresh button) so I'd be tempted to remove it if at all possible! Or we can put it behind the feature flag :)

it was to restore the states of selected edges after undoing. if you could tell me your scenario i can make a fix i think

I can't remember the scenario unfortunately! To be on the safe side, could we add this behind a feature flag? Thanks! :)

Suggested change

call_deferred("refresh_edges")

if ParleySettings.get_setting(Constants.EDITOR_IS_KEYBOARD_SHORTCUTS_ACTIVE, false):

call_deferred("refresh_edges")

Co-authored-by: Jonny Green <me+github@jonnydgreen.com>

- copy shortcut fixes and comment changes

JosephStar318 · 2026-03-07T10:32:13Z

I send my changes. Added the keyboard shortcuts opt-in in project settings as you mentioned.

jonnydgreen · 2026-03-09T20:44:57Z

I send my changes. Added the keyboard shortcuts opt-in in project settings as you mentioned.

Fantastic, thank you so much! I will take a look this week :)

jonnydgreen · 2026-03-20T10:38:09Z

Hello! Apologies for the delay in reviewing this - I had/have to focus on some other things outside of OSS but I should be all good to test, review, and release this in a couple of weeks! :)

jonnydgreen · 2026-05-14T16:08:09Z

Back now! Apologies, that took longer than expected - I've blocked out some time this Sunday onwards to get back into the swing of things and we can get this released! 🚀

jonnydgreen · 2026-05-18T08:08:01Z

Code looks fab, awesome work! Gonna test it out over the next couple of days and go over in a bit more detail but I think we're pretty much there! 🚀

jonnydgreen

Fantastic! Looking over the bezier stuff again was great! 🔥 I've left a few comments to tidy up the code a bit and provide a bit of extra safety, but I think we are there!

The only thing remaining is some documentation but that can be a follow-up PR at some later time - wext stop is merge (squash) and release I think! Well done and thank you!

jonnydgreen · 2026-05-20T20:50:47Z

 	if arrange:
 		arrange_nodes()
+
+	call_deferred("refresh_edges")


I can't remember the scenario unfortunately! To be on the safe side, could we add this behind a feature flag? Thanks! :)

Suggested change

call_deferred("refresh_edges")

if ParleySettings.get_setting(Constants.EDITOR_IS_KEYBOARD_SHORTCUTS_ACTIVE, false):

call_deferred("refresh_edges")

#endregion added back. Co-authored-by: Jonny Green <me+github@jonnydgreen.com>

Co-authored-by: Jonny Green <me+github@jonnydgreen.com>

… enabled

…/parley into keyboard-shortcuts

Co-authored-by: Jonny Green <me+github@jonnydgreen.com>

JosephStar318 · 2026-05-23T08:11:58Z

Suggested changes are done!

jonnydgreen · 2026-05-28T18:47:25Z

Fantastic! I'll merge and release shortly! Thank you again!! 🚀

jonnydgreen · 2026-05-28T19:06:21Z

Submitted the edit to the godot asset library - should be live over the next days or so :)

JosephStar318 · 2026-05-29T08:42:29Z

Nice work!

- created graph operations and handled input from parley grap view

9ac5365

JosephStar318 changed the title ~~- created graph operations and handled input from parley grap view~~ - Keyboard Shortcuts Sep 18, 2025

jonnydgreen reviewed Sep 18, 2025

View reviewed changes

jonnydgreen added the enhancement New feature or request label Sep 18, 2025

Joseph Star added 2 commits September 28, 2025 13:22

- selecting multibple connections, deleting connection and nodes work…

0271472

…s, undo delete WIP

- naming changes

376b719

- delete redo undo cycle mostly done

50aae38

- delete operation improvements

aa310bd

- undo redo history grouped by dialoge sequence ast

jonnydgreen reviewed Oct 26, 2025

View reviewed changes

- bug fixes and improvements

322f9e3

changed a comment

ae8f3df

Co-authored-by: Jonny Green <me+github@jonnydgreen.com>

Joseph Star added 2 commits February 8, 2026 18:44

- bug fixes and improvements

d92b29f

- group selection fix and removed logs

81fe847

This comment was marked as outdated.

Sign in to view

jonnydgreen reviewed Feb 10, 2026

View reviewed changes

- added @tool

348b24b

- changed name connection to edge - removed some of the commented code - added copy function to nodeast - improved duplicate operation - added copy paste support

jonnydgreen reviewed Mar 1, 2026

View reviewed changes

JosephStar318 and others added 4 commits March 7, 2026 12:14

Update addons/parley/models/dialogue_sequence_ast.gd

53d1116

Co-authored-by: Jonny Green <me+github@jonnydgreen.com>

Update addons/parley/models/dialogue_sequence_ast.gd

2eea03b

Co-authored-by: Jonny Green <me+github@jonnydgreen.com>

- comment cheange on id setter method on node_ast

784ba06

- added feature flag and made shortcuts an optional feature

cf989b9

- copy shortcut fixes and comment changes

jonnydgreen approved these changes May 20, 2026

View reviewed changes

JosephStar318 and others added 5 commits May 23, 2026 11:04

Update addons/parley/models/node_ast.gd

5927f3c

#endregion added back. Co-authored-by: Jonny Green <me+github@jonnydgreen.com>

Update addons/parley/views/parley_graph_view.gd

54f66b3

Co-authored-by: Jonny Green <me+github@jonnydgreen.com>

-removed some logs and refresh edges will only be active if shortcuts…

377b7c8

… enabled

Merge branch 'keyboard-shortcuts' of https://github.com/JosephStar318…

e568a0d

…/parley into keyboard-shortcuts

Update addons/parley/main_panel.gd

5d7af23

Co-authored-by: Jonny Green <me+github@jonnydgreen.com>

jonnydgreen merged commit 8189995 into bisterix-studio:main May 28, 2026
1 check passed

	call_deferred("refresh_edges")
	if ParleySettings.get_setting(Constants.EDITOR_IS_KEYBOARD_SHORTCUTS_ACTIVE, false):
	call_deferred("refresh_edges")

Uh oh!

Conversation

JosephStar318 commented Sep 18, 2025

Uh oh!

jonnydgreen left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

jonnydgreen commented Sep 25, 2025

Uh oh!

JosephStar318 commented Sep 26, 2025

Uh oh!

JosephStar318 commented Sep 27, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

jonnydgreen commented Sep 28, 2025

Uh oh!

jonnydgreen commented Sep 28, 2025

Uh oh!

JosephStar318 commented Sep 28, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

jonnydgreen commented Sep 28, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

JosephStar318 commented Sep 28, 2025

Uh oh!

jonnydgreen commented Oct 3, 2025

Uh oh!

JosephStar318 commented Oct 5, 2025

Uh oh!

jonnydgreen commented Oct 12, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

JosephStar318 commented Oct 12, 2025

Uh oh!

jonnydgreen commented Oct 13, 2025

Uh oh!

JosephStar318 commented Oct 18, 2025

Uh oh!

jonnydgreen commented Oct 26, 2025

Uh oh!

jonnydgreen left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

jonnydgreen Oct 26, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

JosephStar318 Oct 26, 2025

Choose a reason for hiding this comment

Uh oh!

jonnydgreen Nov 2, 2025

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

jonnydgreen Oct 26, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

JosephStar318 Nov 16, 2025

Choose a reason for hiding this comment

Uh oh!

jonnydgreen Nov 24, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

jonnydgreen left a comment •

edited

Loading

JosephStar318 commented Sep 27, 2025 •

edited

Loading

JosephStar318 commented Sep 28, 2025 •

edited

Loading

jonnydgreen commented Sep 28, 2025 •

edited

Loading

jonnydgreen commented Oct 12, 2025 •

edited

Loading

jonnydgreen left a comment •

edited

Loading

jonnydgreen Oct 26, 2025 •

edited

Loading

jonnydgreen Oct 26, 2025 •

edited

Loading

jonnydgreen Nov 24, 2025 •

edited

Loading

jonnydgreen commented Nov 2, 2025 •

edited

Loading

jonnydgreen left a comment •

edited

Loading

jonnydgreen commented Feb 23, 2026 •

edited

Loading

jonnydgreen left a comment •

edited

Loading

JosephStar318 Mar 7, 2026 •

edited

Loading

JosephStar318 Mar 7, 2026 •

edited

Loading

jonnydgreen Mar 9, 2026 •

edited

Loading