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.

Sign up for GitHub

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

Jump to bottom

Timings dont Work on Windows #211

Closed
sapphyrus opened this issue Oct 18, 2016 · 3 comments
Closed

Timings dont Work on Windows #211

sapphyrus opened this issue Oct 18, 2016 · 3 comments
Labels
bug An issue that needs to be fixed. Alternatively, a PR fixing an issue.

Comments

@sapphyrus
Copy link

Console Error:
http://hastebin.com/poqojunoxa.sql

Version:
Newest Version from GitHub relases
@bensku
Copy link
Member

bensku commented Oct 21, 2016

Wait what. I'll need to test this on Windows at some point.

Anyway, I strongly advise running any server applications on Linux/anything that is not Windows. At least unless you have expensive Windows Server license.

@bensku bensku added the bug An issue that needs to be fixed. Alternatively, a PR fixing an issue. label Oct 21, 2016
@sapphyrus
Copy link
Author

Yeah, we have a license and the manager wanted to use windows. Can you change the log message to something like [Skript] Timings stopped and results written to "Server/plugins/Skript/timings/..."?

@bensku
Copy link
Member

bensku commented Oct 24, 2016

Ok, figured out what was wrong. Apparently Windows can't handle : in file names.

Meanwhile, on Unix/Linux you can even have ASCII beep...

bensku added a commit that referenced this issue Oct 24, 2016
@bensku
Fix timings on Windows (#211) and add gravity expression (my own stuff!)
b4892d2
@bensku bensku closed this as completed Nov 1, 2016
@BetaBurnt BetaBurnt mentioned this issue May 3, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug An issue that needs to be fixed. Alternatively, a PR fixing an issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bensku @sapphyrus