Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Support own GoTV demos #186

Open
Haxzer opened this issue Jan 8, 2017 · 7 comments
Open

Feature Request: Support own GoTV demos #186

Haxzer opened this issue Jan 8, 2017 · 7 comments

Comments

@Haxzer
Copy link

Haxzer commented Jan 8, 2017

Title says all, I want this because me and my team plays a lot against other teams, and i'd like stats on all these matches that the server records through regular GOTV

@0BuRner
Copy link

0BuRner commented Jan 9, 2017

What tool do you use for managing the match ? eBot ? Standard console commands ? ... ?

@bugdone
Copy link
Owner

bugdone commented Jan 10, 2017

This request keeps popping up (#69, #123, #177). This feature is hard to implement.

A possible solution would be to have a feature that lets users define a new gotv demo type. This would work by configuring a handful of parameterizable heuristics. These could be then shared with the rest of the users.

I didn't really thought about specifics though. Even so, it wouldn't work in every scenario (especially for private gotv servers if the admin issues manual commands instead of having everything automated).

@pz1k
Copy link

pz1k commented Mar 2, 2017

On the time, #177 i worked arround changing the CEVO server name on demo.clj#L71 to GamersClub.com.br and the 'type' to ESEA if im not wrong, but had to run it on my VM since i know nothing about compilling this :/

@bugdone
Copy link
Owner

bugdone commented Mar 2, 2017

If you want to compile this yourself, take a look at the travis file.

A way to implement this feature would be to provide enough settings for the heuristics that the user could create new demo types on his own. But this would mean that the user would be going through demos and trying different settings until they get it right. And of course, at some point they will get to some demo that won't be parsed right as there's no option for that particular case.

A more simpler approach would be to let users just try using the existing heuristics and see if one of the demo types already match their demos.

@spacecow123
Copy link

spacecow123 commented Apr 4, 2017

Doesn't work for demos made using https://github.com/splewis/csgo-pug-setup either. I would be happy to help in any way i can to make this work.

Demos: http://www.cancer10mans.xyz/Demos/

@spacecow123
Copy link

@bugdone

Sorry I'm pretty new to this and was trying to compile using the travis file on my own branch of your project to try and get my servers demos to work on headshot box. Using csgo demos manager my demos parse fine using faceit settings, so I am trying to get headshotbox to identify my demos ace faceit as well. This is the error I'm getting:
image

Is there anything in the travis file I need to change besides the name of the repo and email?

Sorry if this is not the right place to post this.

Thanks!

@bugdone
Copy link
Owner

bugdone commented Aug 4, 2018

In the Travis settings for this project I set 2 environment variables: GITHUB_TOKEN and GITHUB_USER. I think you need to set these in order to get around the rate limit of non-authenticated Github API calls.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants