Jump to content
  • Sky
  • Blueberry
  • Slate
  • Blackcurrant
  • Watermelon
  • Strawberry
  • Orange
  • Banana
  • Apple
  • Emerald
  • Chocolate
  • Charcoal

joserobjr

Members
  • Content Count

    5
  • Joined

  • Last visited

About joserobjr

  • Rank
    Junior Member

Contact Methods

  • Minecraft
    joserobjr
  • GitHub
    joserobjr

Recent Profile Visitors

1127 profile views
  1. I've been trying and searching about it without success... I have a computer with 2 GPUs and 2 screens, I'm trying to use the primary GPU and screen to render a GUI and the second pair to show the application log. I also tried to copy the term lib in attempt to have a parallel term, but term2.write still writes to the main screen... This is what I have so far: local term2 local primaryGpu = component.gpu local primaryScreen = component.screen ---@type component.gpu local secondaryGpu ---@type component.screen local secondaryScreen for gpuAddr in pairs(component.list("gpu")
  2. Thank you TYKUHN2, I thought about using string.dump() before and some lua obfuscators use it to obfuscate but I couldn't find a way to load the data, stringload() does not exists and load() is limited to read only text.
  3. This is cool, please share it, I wanted to use it on my mining robot's remote control
  4. I'm writing an advanced mining robot on a server that I play and I want to sell it to other players, I've been working on it many hours in 2 weeks so I really want to receive a reward for it on the server. I'll be selling robots ready to go and dedicated for my software, I'm planning to release the source code in future but until there I don't want to see pirated floppy disks being sold cheaper I thought about fleshing an EEPROM or running it directly on init.lua (I don't really need the OpenOS to execute the software, it's independent) but other players could easily steal the EEPROM on a
  5. If it get updated to 1.9, please, don't stop updating 1.7.10
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use and Privacy Policy.