|
|
| Line 3: |
Line 3: |
| <span class="badgeicon-med-withborder">[[File:Witcheffect.png|25px|link=]]</span> '''[https://witcheffect.com Witch Effect]''' | | <span class="badgeicon-med-withborder">[[File:Witcheffect.png|25px|link=]]</span> '''[https://witcheffect.com Witch Effect]''' |
|
| |
|
| ==4Chan Cup Ideas== | | ==4Chan Projects== |
| ===[https://www.youtube.com/watch?v=eW6sEkTGbUc Database]===
| | This is a condensed version of what I wrote earlier, you can check the page history for that.<br> |
| First would be moving everything to a database, from which functions from the records page to the cup pages to the board pages could be 90% automated.<br>
| | [https://trello.com/4chancup Trello page] for progress<br> |
| [https://cdn.discordapp.com/attachments/320905898220584960/438666577487986708/20180425_074250.jpg Database Schemas]<br> | | ===Stream Chat=== |
| To summarize, there'd be tables for pretty much everything, Cups, Matches, Goals, Fouls, Benaldies, Rosters, etc.<br>
| | This is the highest priority item right now since there's no confirmation that cytube can handle up to 3500 users in a chatroom.<br> |
| This rough draft encompasses any PES cup; I'd say starting from scratch, it'd take a couple of people a month to get all official cups and /vg/l entered in. I wouldn't have a guess on invitationals because of their more spotty record keeping.
| | Current alternatives would be to: |
| | * Use the stream's native chat service (Not ideal since we want a static link for people to use and remember) |
| | * Running our cytube server and customizing it (I tried and I failed to get it running) |
| | * Using IRC (May be too difficult for people to use) |
| | * Creating something from scratch (High chance it'll be awful) |
| | Deadline: July 20th, 2018 (One week before summer cup) |
|
| |
|
| Essentially, each cup would have it's own ID and anything regarding that cup can be tied back to that ID, which will be used for some of the other ideas listed below.
| | ===Polls=== |
| | Having polls that are intuitive will increase participation, especially when they can be customized to a board's culture.<br> |
| | I have the basic framework ready and just need to be able to let managers create their own polls without asking me.<br> |
| | This needs to be done fairly quickly as well for the cup logo poll.<br> |
| | Deadline: June 30th, 2018 |
|
| |
|
| | ===SQL DB=== |
| | The sooner this is done the easier it'll be to maintain in the long run. Interfaces are set up and running, but the matter of connecting it to the wiki is up to debate right now.<br> |
| | The bulk of this effort will hopefully be done by volunteers.<br> |
| | Deadline: August 31st, 2018 |
|
| |
|
| ===[https://www.youtube.com/watch?v=Yik5P7Gcf2c Cup Pages]=== | | ===TurboAATF=== |
| The ability to sort matches either by group, or by date. <br>
| | I hope to delay this until PES19 if we do move to it. There doesn't seem to be any major rule changes that'll require the rewrite immediately. <br> |
| Displaying the rosters from that cup, hidden by default.
| | Deadline: TBD |
|
| |
|
| | ===Rigdio=== |
| | Same with TurboAATF. <br> |
| | Deadline: TBD |
|
| |
|
| ===[https://www.youtube.com/watch?v=ZEBGCOCxLgA Editor/AATF]=== | | ===Export Manager=== |
| I'm not exact on what Archie was aiming for with Turbo AATF, but I've put some thought into creating a rules engine for AATF that allow for anyone to create their own Rule Books. It'd be much faster to manually update AATF, but with the other proposed changes, this may be worth it. My current thoughts:<br>
| | This is a fairly large project and will require all the former to be completed really for this one to be effective. It will essentially be rigcloud but connected to everything else, so your tactical, aesthetic, and audio will be synced to the cloud in a standardized format, and streamers won't have to do a thing. |
| Flow:
| | Deadline: Dec 31st, 2018 |
| =====Cup Host=====
| |
| 1. Select Cup ID/Name <br>
| |
| 2. Create New Ruleset (Eg. Height Abuse)<br>
| |
| 3. Create Squad Rules (Eg. Min 2 GKs, 9 Players at 194cm)<br>
| |
| 4. Create Player Rules (Eg. Max 2 Weak Foot Accuracy if above 180cm)<br>
| |
| 5. Create Medal Rules (Eg. Max 99 Stats All, -4 Stats if above 190cm)<br>
| |
| =====Manager=====
| |
| 1. Select Cup ID/Name<br>
| |
| 2. Select Team<br>
| |
| 3. Select Ruleset<br>
| |
| 4. Create team online<br>
| |
| 5. Download either EDIT/TEXPORT file to use<br>
| |
| | |
| I'm not quite confident yet in this system being both flexible and easy to use, but it should allow for the creation of /sp/ bowl, /vg/l, and 4cc rules. <br>
| |
| I do have interest though in moving this to the web so you can just upload a TEXPORT and have the server check for you, which will be useful to the Rigcloud. Would require collaboration with scoops to integrate the editor.
| |
| | |
| | |
| ===[https://www.youtube.com/watch?v=pGriqJwEYeE Streamer Tools]===
| |
| I have not looked at Rigdio, but I'd plan to move that to the web as well. Being on the web, it would not include chants or anything PES dependent.<br>
| |
| Flow:
| |
| =====Preparing Music=====
| |
| 1. Manager logs on to page<br>
| |
| 2. Manager selects cup and team<br>
| |
| 3. Manager uploads music<br>
| |
| 4. Manager selects the criteria (If using the online editor, they'd have the player names listed already)<br>
| |
| | |
| =====Streamer=====
| |
| 1. Streamer logs on to page<br>
| |
| 2. Streamer selects cup and playing teams<br>
| |
| 3. Streamer clicks on buttons same as with Rigdio, no downloading required<br>
| |
| | |
| I had ran a cup in PES 2015 with some friends who watched the 4CC, created their own teams, but had no ideas on managing and no real reason to install PES and read up on tactics. For the next cup that never happened, I started some work on live managing tools for them, one of which I recovered is <b>[https://witcheffect.com/4cc/bkc/live.php this]</b>, which was planned to be the managing screen so they can play around it and also use it to speed up live managing by making the changes themself, to which I, the streamer can just look at without waiting for text instructions.
| |
| | |
| Ideally, these tools should be executables that can be run locally as well so they can pull data from PES.
| |
| | |
| For pastebins, it might be worth integrating complex ones into SENPAI so that it can immediately alert the streamer of instructions when criteria are met. This one could be important, but I've not given it much thought beyond the idea. The backend commmunication with PES is also out of my realm.
| |
| | |
| | |
| ===[https://www.youtube.com/watch?v=7iVXEMyQnpA Rigcloud]===
| |
| What ties stuff together.<br>
| |
| Flow:<br>
| |
| 1. Cup Host creates an entry for a new cup in the database. <br>
| |
| 2. Cup Host can create a whitelist of teams if desired.<br>
| |
| 3. Board Managers and others will log in to RigCloud.<br>
| |
| 4. User select the cup name and team (If going by the online editor, their roster would be created already)<br>
| |
| 5. User select player and uploads the player's face folder<br>
| |
| 6. User uploads kit .bin files, updated logos, whatever other single files<br>
| |
| 7. System automatically names and places contents in a correct folder (Assuming player IDs would be in the database, which it should be)<br>
| |
| 8. There'd also be the ability to upload overall stuff such as swipes, stadiums, and ボール<br>
| |
| 9. User, if authorized (To prevent server overload), can then ask the server nicely to compile the cup CPKs. <br>
| |
| | |
| | |
| ===[https://youtu.be/dcEpj8ZcRd0 Final Thoughts]===
| |
| The goal for a lot of this stuff is to bring everything together onto one central database to reduce time spent waiting on humans who invariably go to sleep or work or school.
| |
| I see the core features being feasible before summer barring something comes up IRL, there are some issues that I can see however. I'm not deeply involved with the cup so alot of this stuff might be stuff already being done or decided against.<br>
| |
| 1. A lot of this work would be wasted if this was the last cup on PES 2017, even if Summer was the last cup for it, it'd still probably suck. The workload to update to 2018 is unknown as I know nothing about it.<br>
| |
| 2. Some of this stuff moves the site away from being a wiki, a lot of these pages would be just interfaces to the SQL server which if closed off to selective user access, would kill the ability for people to make random teams and pages, this wouldn't stop that really, but those teams would exist outside the <s>Matrix</s>Database. Hard for me to put into words, but yes, but this would probably make things less open, I'm not sure how often the wiki is subject to vandalism.<br>
| |
| 3. There is the ability to do SQL calls from the wiki editor, I'm not quite sure yet if these can be made easy to make tags like (Player|Goals|Official) to display a player's official goal count.<br>
| |
/mu/
/uboa/
Witch Effect
4Chan Projects
This is a condensed version of what I wrote earlier, you can check the page history for that.
Trello page for progress
Stream Chat
This is the highest priority item right now since there's no confirmation that cytube can handle up to 3500 users in a chatroom.
Current alternatives would be to:
- Use the stream's native chat service (Not ideal since we want a static link for people to use and remember)
- Running our cytube server and customizing it (I tried and I failed to get it running)
- Using IRC (May be too difficult for people to use)
- Creating something from scratch (High chance it'll be awful)
Deadline: July 20th, 2018 (One week before summer cup)
Polls
Having polls that are intuitive will increase participation, especially when they can be customized to a board's culture.
I have the basic framework ready and just need to be able to let managers create their own polls without asking me.
This needs to be done fairly quickly as well for the cup logo poll.
Deadline: June 30th, 2018
SQL DB
The sooner this is done the easier it'll be to maintain in the long run. Interfaces are set up and running, but the matter of connecting it to the wiki is up to debate right now.
The bulk of this effort will hopefully be done by volunteers.
Deadline: August 31st, 2018
TurboAATF
I hope to delay this until PES19 if we do move to it. There doesn't seem to be any major rule changes that'll require the rewrite immediately.
Deadline: TBD
Rigdio
Same with TurboAATF.
Deadline: TBD
Export Manager
This is a fairly large project and will require all the former to be completed really for this one to be effective. It will essentially be rigcloud but connected to everything else, so your tactical, aesthetic, and audio will be synced to the cloud in a standardized format, and streamers won't have to do a thing.
Deadline: Dec 31st, 2018