<?xml version="1.0"?>
<rss version="2.0">
   <channel>
      <title>Aidan Dougherty by Friends Select</title>
      <link>https://padlet.com/FSSseniors2021/aidand</link>
      <description>Senior Independent Project</description>
      <language>en-us</language>
      <pubDate>2021-04-19 13:07:59 UTC</pubDate>
      <lastBuildDate>2024-11-17 02:58:35 UTC</lastBuildDate>
      <webMaster>hello@padlet.com</webMaster>
      <image>
         <url></url>
      </image>
      <item>
         <title>3D Multiplayer Game</title>
         <author></author>
         <link>https://padlet.com/FSSseniors2021/aidand/wish/1567479304</link>
         <description><![CDATA[<div>I'm going to make a 3D multiplayer game in Godot. Godot is a popular game engine that is very easy to work with. The 3D part won't be too bad, but the networking part will be a challenge because I've never done it before. The server handling all the packets will be written in Go, probably the most popular language to write a server in at the moment.</div>]]></description>
         <enclosure url="" />
         <pubDate>2021-05-28 03:37:08 UTC</pubDate>
         <guid>https://padlet.com/FSSseniors2021/aidand/wish/1567479304</guid>
      </item>
      <item>
         <title>First Day</title>
         <author></author>
         <link>https://padlet.com/FSSseniors2021/aidand/wish/1586745218</link>
         <description><![CDATA[<div>I started messing around with Godot to get more familiar with it so I can develop freely later on. I also started on my server that will handle all the packets that will be transferred from the client to the server, then sent out to all other clients connected. Right now, I have been sending simple data to the server just to test that everything is working. Later on, I will start compressing all packets so I can send lots of data without it being too slow. I'm still deciding which type of packets to use, but I am leaning towards TCP because it's easier to deal since the server doesn't need to verify that all the packets have came in (pretty much just allows packet loss).</div>]]></description>
         <enclosure url="" />
         <pubDate>2021-06-05 08:01:53 UTC</pubDate>
         <guid>https://padlet.com/FSSseniors2021/aidand/wish/1586745218</guid>
      </item>
      <item>
         <title>Server Trouble</title>
         <author></author>
         <link>https://padlet.com/FSSseniors2021/aidand/wish/1586748274</link>
         <description><![CDATA[<div>I am having a lot of trouble with handling and reading all the packets from the clients. Since Go isn't as much a high language than Node.JS, I need to do a lot of the work myself. I first needed to have an infinite loop for all clients to keep looking out for incoming packets, so each client had its own goroutine so we don't have to keep looping over the client list and look for packets one by one. We just take advantage of Go's really easy way to multi-thread our program. After looking for all the packets, I had to decompress them with ZLib and translate the ASCII data to data I could read. The most difficult part was probably figuring out what datatypes to assign data since it can be hard. Some common tricks are adding a zero terminator to strings, which are usually longer.</div>]]></description>
         <enclosure url="" />
         <pubDate>2021-06-05 08:07:29 UTC</pubDate>
         <guid>https://padlet.com/FSSseniors2021/aidand/wish/1586748274</guid>
      </item>
      <item>
         <title>Got Clients Moving!</title>
         <author></author>
         <link>https://padlet.com/FSSseniors2021/aidand/wish/1586751157</link>
         <description><![CDATA[<div>I finally got everything working at its most basic level. What I have now is 2 blocks with one central camera moving around on each others screens. What I have is if the blocks move (e.g. they press W, A, S, D, or space), then send the current position to the client. The server will then receive that data and broadcast it to all other clients so it'll look like it was moving to everyone else in the game.</div>]]></description>
         <enclosure url="" />
         <pubDate>2021-06-05 08:12:38 UTC</pubDate>
         <guid>https://padlet.com/FSSseniors2021/aidand/wish/1586751157</guid>
      </item>
      <item>
         <title>Chat Feature</title>
         <author></author>
         <link>https://padlet.com/FSSseniors2021/aidand/wish/1586754144</link>
         <description><![CDATA[<div>Since I got the hard moving around part done, I decided to make a little chat system in game for all the clients. Now once a client is connected, they are given a unique id and name (player1, player2, etc.). Clients can chat to each other by pressing&nbsp;'t' and writing their message in the little textbox. Their message will be send to the server then broadcasted to all the other clients. But unfortunately, this broke the movement system since the server now has no idea if it is receiving a chat packet or a position packet. So I quickly fixed this by setting a Uint8 at the beginning of every packet determining which type of packet it was. 1 = position packet and 2 = chat packet. This will make the game much more scalable if I decide to develop this past this internship.</div>]]></description>
         <enclosure url="" />
         <pubDate>2021-06-05 08:16:52 UTC</pubDate>
         <guid>https://padlet.com/FSSseniors2021/aidand/wish/1586754144</guid>
      </item>
      <item>
         <title>Aidan Dougherty</title>
         <author>FSSseniors2021</author>
         <link>https://padlet.com/FSSseniors2021/aidand/wish/1588112218</link>
         <description><![CDATA[<div>Coding</div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/1215752985/3f712782f8b6f544e1a47becc15fa351/IMG_1615.MOV" />
         <pubDate>2021-06-06 16:32:56 UTC</pubDate>
         <guid>https://padlet.com/FSSseniors2021/aidand/wish/1588112218</guid>
      </item>
   </channel>
</rss>
