Jump to content

xlr100

Member
  • Posts

    76
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by xlr100

  1. Good job. Although the code isn't efficient, the idea is good and you managed to execute it
  2. I was bored so i fixed some stuff and added some stuff, its a lot more efficient as well https://pastebin.com/Z47AJaT8
  3. A good idea, although it can be executed better and have more added to it. Btw, what did you make the second command for?
  4. I don't want to discourage but you should always use list variables in case of storing the same kind information for different objects. For example, a variable like {rank.%player%} is only specific for 1 player (not to mention that using player instead of uuid of player isn't good for cases of storing long living data). If you use {rank::%uuid of player%} you can loop the variable, compare the ranks, clear the whole list if necessary and make a leaderboard of the var (although a leaderboard isn't useful in this case). As for the argument of keeping things simple, if you intention is to make it easy to understand for others than its counterproductive. If someone truly cannot understand lists, using them will help him do so and encourage him to learn. On the other hand, not doing so and ignoring the existence of lists will make the reader ignorant of lists. This logic applies not only to lists, but to coding techniques and the likes. Sorry for the long message but just wanted to clear this out, as this mistake is made often
  5. xlr100

    Making scripts

    Make a chat bot that answers your questions and communicats with you. The challenge isn't neccecerly in the coding skills but more in the determination
  6. name of inventory doesn't work currently, as long as many other things. Instead of that you can make a list of players in the indexes and the name of the inventory in the values, and check the value of a player to find out his inventory
×
×
  • Create New...