Skip to content

Latest commit

 

History

History
42 lines (33 loc) · 2.37 KB

VERSION.md

File metadata and controls

42 lines (33 loc) · 2.37 KB

Changelog

0.0.8

  • Added a new feature for ops to cast QEMU commands directly.
    • /w botnick obey_one system_reset
    • /w botnick obey_all ayylmao
    • Note: They can't change_mode or something game-related (yet).
    • issue #30
  • Scaled the whole code to pass JSHint linting.

0.0.7

  • Added a new filter mechanism.
  • Added the command change_mode.
    • Users can vote to change the current play-mode. There is also a mode_can_change = true for admins to toggle.
  • Fixed a mouse movement bug. It should work fine now (if it doesn't, it's qemu).
  • Chaos mode structure improvement, specifically the quotes.

0.0.6

  • Added a new chaos mode.
  • Fixed a minor bug related to voting mouse movement.
  • Minor code improvements.

0.0.5

  • Added monarchy mode.
  • Minor code-structure improvement.

0.0.4

  • A new blacklist mechanism has been added.
    • You can add entries in blacklist.json, if any of those entries occurs in some username on input, the input is simply ignored and not taken into account.
    • issue #17
  • A couple additions in map.json.
  • A new mouse mechanic is introduced.
    • You can mouse_move_x, mouse_move_y and mouse_move_z to control mouse movement. Upon initiation of those commands, a voting process starts with integers only being accepted as individual votes. Let i be the winnning vote of mouse_move_[x/y/z], the mouse will move i pixels. You can also mouse_left, mouse_middle and mouse_right to control the mouse buttons. Use mouse_[left/middle/right]_double for a double click. Due to security, there is a minimum and maximum of dx, dy and dz which are set at the global variables settings section in twitch_master.js. The only downside of this is when some admin interacts with the VM, that would mess the current dx, dy and dz values. I don't believe there is anything we can do about this, feel free to suggest something.