Confirmed. Thanks. Issue #56.
- danBhentschel
Version 0.2.12 has been published to the Chrome Web Store and should be rolling out to clients now. Other than some minor ground work to pave the way for a Firefox and an Edge version (not yet available) the only change is a fix for Issue #56.
FYI⌠Version 0.2.13 of CG Spunk has been submitted to Mozilla and is awaiting approval. Since Mozilla approval is a manual process, itâs hard to know exactly how long it will take. CG Spunk is currently in queue position 248 of 282 after a few days of waiting.
If you want to test it out for yourself, you can load it as an unsigned add-on by downloading Firefox Developer Edition and then following the instructions in this FAQ (What are my options if I want to install unsigned extensions in Firefox?) The Firefox add-on can be found here:
https://addons.mozilla.org/en-US/firefox/addon/cg-spunk/
Thanks for all the work youâve done on this⌠your tool is indispensable for all us bot programming fans.
Version 0.2.14 has been published to the Chrome Web Store and should be rolling out to clients now. It has also been published to Mozilla, though itâs still unsigned at this point (203 / 264 in the review queue). Changes in 0.2.14 include:
This Game log screen is customizable to show the game information that you are interested in. NOTE that the stdin information is not provided in the CG APIs (that I know of) and so you will need to put it into your stderr output in the following format:
IN
stdin content (as read from stdin) should be echoed here
/IN
stderr content can go after the IN /IN pair.
If you format your stdin inside the stderr following this format, then CG Spunk will detect it and display it properly on the Game log screen.
Version 0.2.15 has just been published to both Chrome and Firefox (still unsigned⌠187 in the queue). It fixes Issue #59, pointed out by @Tiramon. Thanks!
Version 0.2.16 has just been published to both Chrome and Firefox (still unsigned⌠185 in the queue). It âfixesâ Issue #62.
This is likely to be a controversial change to the extension. I recommend you read the Issue text. Here is a summary:
@_CG_Maxime has requested that I put a delay between matches to reduce the load on the server. At some unspecified point in the future (soon?) CG will enforce a limit to number of matches played within a certain time period. Itâs unclear at this time what is a suitable delay, and so I have made the value (for now) fully configurable, with a default of 30 seconds. In the future, I may enforce a minimum delay, or just hardcode a fixed delay value. Weâll see where this goes.
Also note, once the extension updates to v0.2.16, it will initially be disabled because I have added a new required permision: Display notifications. You will need to accept this new permission before it will work again.
I guess it was unavoidable given the popularity of the tool.
Hi, I love what youâre doing with CG Spunk, moreover these changes were definitely needed!
But what about the other new permissions:
I knew this question would come up. Iâve actually hit it before with other extensions Iâve written.
That âpermissionâ was always there. It isnât new with this version, and it comes when I use the chrome.tabs API. You can see all the âspecialâ APIs that Iâm using in the manifest.json file (in the âpermissionsâ section).
It can be challenging to do much of anything in a Chrome extension without using chrome.tabs in some fashion. Itâs pretty much the general purpose API, and it has a horribly labeled (to the user) permission: âRead your browsing historyâ???
It actually doesnât give the extension the ability to peruse your history. That functionality comes through the chrome.history API, which I am NOT using. You can see a (one of many) discussion on the misleading wording of this permission here:
https://bugs.chromium.org/p/chromium/issues/detail?id=429185
Thanks for keeping me honest.
Thank you for all this additional information, I donât know much about those APIs, thatâs why It immediately caught all my attention
Thank you again for your great work and your reactivity to answer
Thank you player_one for the modification. We like CG Spunk and we donât want to block it, but if such a tool become popular it may degrade the user experience for everyone. A delay sounds like a good solution to avoid flooding continuously the plays. Be careful, there are several quotas (for 1 minute, 5 minutes and 15 minutes), so if you reduce that delay too much you may be blocked for the next 15 minutes.
I think asking to âplay niceâ with very vague indications as to what you are actually allowed to do is counter-productive for everyone. Please be more transparent and give real numbers on the âquotaâ everyone is allowed to use. I am aware you are experimenting and probably tweaking them still, but keep us updated and we will adjust accordingly.
As it stands, the arbitrary 30 seconds put by default will make getting results on GitC take 5 times as long as before, which is a huge deal. Even if player_one enforces a minimum limit without configuration, as a community of developers it will be a piece of cake to fork the code and remove it.
It is already difficult enough to have good information on the impact of your changes when you reach the top 20. Limiting the ability to do so on top of having to guess how much we can actually get away with is too much.
There has to be a better solution.
As explained here, CG Spunk uses the play service call to compute the battles. The problem is that these plays are computed with the highest priority which has two consequences:
The battles computed by CG Spunk should have the same priority that the ones computed in the arena. Thatâs not currently possible and we donât have the time to implement that before the end of the contest.
The strictest limit should be 50 plays in 15 minutes (but we may reduce this value), which is a play every 18 seconds during 15 minutes.
Thanks for the explanation! I understand the reasoning for the limit due to how the servers operate right now. I was much more concerned we had to guess how much was enough and possibly take a 15 minutes timeout if we end up guessing wrong, which is really detrimential at this stage of the contest. With the numbers you provide it will be much more fair, so thanks!
two consequences:
I see a third consequence. If players develop their AI locally without the need to push them on the leaderboard, then many hidden AIs improvements will pop-up at the end of the contest.
I wonât make a strong case for it, but I appreciate that before CG Spunk it was possible to see people pushing their AIs even when they tried to keep everything hidden.
CG Spunk is an amazing tool outside of contests, it just doesnât feel right to allow it in contests.
The problem is that the arena during a contest only gives you 100 games. So youâll play ⌠5 games against each player in the top 10 ? Well, better write an AI with a random()
and pray.
The reason because many players use CG Spunk is because itâs currently the only way to really test your AI against the players around your rank in the arena. We just have no other choice.
If tomorrow Codingame add the possibility to do a 1000 games submit, CG spunk will be useless.
A game can last 20 seconds (for this contest), 1000 games requires a total of 5 hours of computing. There are approximatively 80 processors available for the computation of the games. With more than 3000 players, itâs not possible right nowâŚ
However, we will add more battles for the legend league.
Version 0.2.18 has just been published to both Chrome and Firefox (still unsigned⌠116 in the queue).
Fixes a couple of bugs:
And a couple new features:
Version 0.2.19 has just been published for Chrome. Note that I have not updated Firefox with this change yet. The new behavior doesnât work very well on FF, and I donât have time to debug it right now.
So after using it for a while, Iâve decided that the auto-opening log window is too annoying. In particular, I donât like how it keeps opening new windows on various locations on my screen. SoooâŚ
I fixed it! The log window will now close and re-open when doing a new Play operation from the IDE, and it will remember previous size, location, and option selections.
Issue #69: Close and re-open game log window when clicking Play from the IDE