Some Noob questions

  • settings.readString stores the string in the devices flash memory; this will let you save the data to the device. here’s a quick example of using it to store a message for future players (like you would save data, so that you could save the data as the player progresses, and try to read it whenever they reset the device): https://makecode.com/_3uF6WxXu9VX7

2019-12-24 00.09.39

  • You could handle it with overlaps, it might be a bit tricky though - you would probably end up wanting to figure out which direction the player is coming from (based off their velocities), and reset the position to be opposite that direction when they hit one of the sprites - e.g. if the player is moving right and they overlap an enemy, set the player’s .right position to the enemies .left position: https://makecode.com/_15bRj9cL5crA

other potential approaches:

  • make the other ‘sprites’ walls if they aren’t moving, and let the physics take of them / handle the collections with wall collision handlers.
  • the tileworld extension handles things like this nicely by aligning sprites to the grid, but I’m not sure if the current state is fully stable / if there is any documentation (@tballmsft). Also, the extension linked in that post is a bit older; now located here

(re: hardware multiplayer, I haven’t personally interacted used it / made any multiplayer games on hardware yet, and there will likely be more iterations before that part of the codebase is fully stable)

1 Like