Git Product home page Git Product logo

kitboga-codeville's Introduction

kitboga-codeville

This repository is designed to host Twitch Streamer and YouTuber Kitboga's community-made scripts. Pull requests are welcome, but will be filtered closely.

Contributing

Most of the discussion around this repository should happen within the official Kitboga Discord's #codeville channel.

Please join the discord here!

Development primarily consists of two methods. They are issues and pull requests. As a general rule of thumb, issues reveal parts of the code that need to be upgraded, and pull requests submit changes. New scripts can request to be added by creating a pull request with that code included. Issues can be created, then the changes submitted through a pull request. Be sure to mention in your pull request which issue it resolves with #<issue number>.

Any new programs submitted with a PR should placed in a folder as such: <repo>/Unofficial/<language>/<project> e.g. <repo>/Unofficial/AHK/ahk-windowphysics.

KitbogaCodeville Organization

The KitbogaCodeville GitHub Organization is maintained by the public and new members will be invited based on activity. If you wish to be a code reviewer, please message a member of the Organization. Being a member of the Reviewer group will not grant you any special permissions to edit the repository, but will allow you to submit code reviews on pull requests.

Review Guide

All submitted changes are reviewed by the community. In order to submit a review, pay close attention to each line of code and be wary to watch for any malicious content. The nature of this repository treads a fine line between fun programs, and unwanted behaviour. Additionally, be sure to run the program for functionality after reading through the code. Check for proper placement of the files in their subdirectories. Do not approve changes if there is anything that you see requires a change. Simply note the section that requires changing, and leave a request for change.

kitboga-codeville's People

Contributors

gabdube avatar gohtar avatar jyeguru avatar kthays avatar llemonduck avatar niboty avatar pause009 avatar thedevfreak avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

kitboga-codeville's Issues

Simplify funky-numbers.ahk mode switching

This script gives the ability to type numbers either one-off, or as another random number. As it stands currently, this script requires a chunk of lines to be commented out/in to change. By adding a mode switching variable, with if statements, this switching could be changed by changing one variable.

Add ability for client to accept only certain types of messages (RC API)

Add support for an optional accept object in the Remote Control API GET request. This will be a querystring value by necessity of being GET and not POST.

Suggestions:

  • &accept=showimage,messagebox
  • &accept=showimage&accept=messagebox

If set, this would be used to filter the DB objects returned when polling and only the matching objects sent/deleted, any non-matching objects remain in the table to be fetched by other clients/polls.

Standardization of AHK hotkeys/toggles

So with the increasing amount of AHK scripts that are being developed for use on the stream having different hotkeys for all of them will become impossible to remember. I suggest we standardize the keys used in hotkeys as well as what hotkeys/functionality a script requires.

The following are my initial suggestions, feel free to give input!

Standardized Hotkeys:

  • 3 key input, 1st being standard, 2nd being script specific, 3rd being script options/toggles
  • For the 1st key I suggest something on the lower left like Alt
  • For the 2nd key it should probably be within 1 hand range of the 1st key, I suggest the left half of the letters on the keyboard.
  • For the 3rd key it should have enough options for the script, I suggest any of the numbers.

Functionality All Scripts should have:

  • Standardized Exit app hotkey so Kitboga could shut down all scripts at once. ex: Ctrl + Esc
  • Additional Script Specific exit app hotkey ex. Alt + [ScriptSpecificKey] + Esc
  • Ability to Pause/stop ex. Alt + [ScriptSpecificKey] + 0
  • Any options that the script has on functionality should be broken into the most common configurations/settings and be able to be toggled between using Alt + [ScriptSpecificKey] + [1-9]

Let me know what you think. With hotkeys I feel like we need to consider accidental triggers (3 keys should be good enough), memorability, and the ability to actually press all the keys

ahk-notepad does not prevent pasting

Two forms of pasting are available to the scammer, Ctrl+V (which was prevented during stream with a ~^v:: return intercept) and right-click + paste. The first can be easily added but I will leave the second as an exercise for a new contributor.

Discord Bot Integration

Is Discord Bot integration worth adding? For implementation, the source can be hosted here, and for hosting I can host and run the Discord Bot to send updates and enable commands in order to allow some basic Issue/PR queries/updates to be sent to the Discord channel if approved by the staff team.

Is this something people would be interested in having?

It enables more people to be exposed to the repository and see changes more frequently, although it also adds extra messages to the channel when an updates happens to the repository.

Sort scripts by official and unofficial

I propose that scripts written or used by Kitboga be placed in a separate root folder, to differentiate community-submitted scripts from stream-created scripts. Open for discussion.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.