Are you getting any results from regionals? What format are we getting them in as? I'm curious if anyone ignored the FFG software and still went with Cryodex. Not that I want their software to fail, just curious what the current consensus is on it.

I assume we're going with the ordering as displayed on the FFG sheet.

Also, can we 0-index them? So we'll have "asteroid-0", "asteroid-1", ..., "asteroid-5", "debris-0", "debris-1", ..., "debris-5". Or should they be generic obstacles? E.g. "obstacle-0" through "obstacle-11"?

Cant you list them from smallest to largest? That's what I do with my debris tokens when putting them away. Food for thought.

Edit:

Oh, also, that way people will kinda know which one you talk about and don't need to memorize a chart. 1's and 2's are the largest asteroids and derbies fields, 3-4 is the medium ones, and 5-6 are the smaller tokens. In terms of surface area of course.

added a 'regional' filter to the charts page http://lists.starwarsclubhouse.com/charts

Are you getting any results from regionals? What format are we getting them in as? I'm curious if anyone ignored the FFG software and still went with Cryodex. Not that I want their software to fail, just curious what the current consensus is on it.

nothing yet!

re: ordering, yeah.

re: 0-indexing, I prefer that too

re: embedding type into name, I prefer "asteroid-0" and "debris-0" versus "obstacle-0"

What about going with the set that the obstacle in question was first released in, zero-indexed left-to-right as per the squad sheet?

So we'd have "core-asteroid-0", "core-asteroid-1", ... "yt2400-debris-0", ... "vt49decimator-debris-3" etc.

I've been thinking about this a bit recently and I'm not sure that saving asteroids alongside a squadron is a good idea for a squadron builder. I don't want to have everyone's squadrons multiplied by the number of different obstacles they have flown them with. Ie. Saving a BBBZ list with asteroids 1-3 and BBBZ with asteroids 4-6 shouldn't really be two different squadrons. In casual games, many people will use a variety of obstacles with the same squadron, so obstacles need to be optional.

My solution was going to be to have something on squadron printouts where users could tick or circle the obstacles they are using. But, of course, this means that while you could still hand a printout to a TO, the obstacle data won't be part of the squadron's XWS.

Could we perhaps separate out the squadron XWS and the obstacle XWS into 2 different things?

voidstate

I'm fine with the XWS spec listing obstacles as optional, and builders not fully supporting them as part of their export.

However, the point of the spec is to contain everything about a tournament-legal list, and right now that includes obstacle choice, so I don't think it makes sense to have the obstacles stored elsewhere.

I suspect that most people aren't going to bother to pick rocks for 99% of the lists they make. I know I wouldn't for casual games, and probably not for most lists I'm going to bring to a tournament, unless I think it's likely that there will be some QR code / auto import stuff going on.

agreed. at minimum let's stash them in the spec. if we decide it makes sense to a) implement them in the list builders and b) pass them into juggler, let's do that then.

couple of updates:

1) no word yet the regional data from this weekend. juggler, can you bump that email thread?

2) eli added the new tie advanced pilots to the spec and I've rolled them out to listjuggler.

3) I'm close -- CLOSE! -- to getting search working. It was some icky sql, but hey, nearly there. search will exhibit itself as a search bar where you can type in arbitrary boolean expressions; for example 'p:Dash and p:Chew' (all the Chewbacca & Dash lists), 'p:Chiraneau and ( p:Soontir or s:lambda)' (all the chiraneau plus soontir or lambda lists), etc.

Say I wanted to contribute to Cryodex or List Juggler...

Is the source code for either of these hosted on Github or some other public repositoty?

Sozin, I talked to the guy from the WV regionals and he is going to be uploading his Cryodex JSON output soon. I have yet to hear from a regionals that used the FFG software.

If you need any help with SQL let me know. Half of my career is searching for data and displaying it on the screen. The other half is changing it and putting it back.

Say I wanted to contribute to Cryodex or List Juggler...

Is the source code for either of these hosted on Github or some other public repositoty?

Anything inparticular you'd like to help with? For Cryodex, you are welcome to create any widget or page you'd like and I can incorporate it into the program. For example, lots of people hate the manual pairing change window. If you want to make something better you're welcome to it. I can supply code for any relevant classes.

Say I wanted to contribute to Cryodex or List Juggler...

Is the source code for either of these hosted on Github or some other public repositoty?

ListJuggler: https://github.com/lhayhurst/xwlists ; there's a basic readme there (thanks geordanr :-) )

Sozin, I talked to the guy from the WV regionals and he is going to be uploading his Cryodex JSON output soon. I have yet to hear from a regionals that used the FFG software.

If you need any help with SQL let me know. Half of my career is searching for data and displaying it on the screen. The other half is changing it and putting it back.

Cool, ty, I might take you up on that. I'm generating all the sql through the SqlAlchemy library , so I never actually explicitly write sql code in the application. Normally the queries are pretty simple, but in the case of search, it is a bit tricky, as I am code generating the boolean expressions into sql at run-time.

2) eli added the new tie advanced pilots to the spec and I've rolled them out to listjuggler.

I'll probably push those out late tonight or tomorrow. The wife wants to watch Age of Ultron for our anniversary tonight, and I'm sure as heck not going to mess that up. "Yes, dear!"

All that's left is to verify that the "obstacles" key validator is working, and it should be ready to go.

I've been meaning to try adding some search capabilities to LJ as well, and I used SQLAlchemy in a previous life (adding some of the API endpoints reawakened some of that knowledge). I may muck around.

Search is live!

http://lists.starwarsclubhouse.com/search

Implementation: https://github.com/lhayhurst/xwlists/blob/master/search.py

XWS updated to v0.2.1 (backwards compatible change, so no beta-major version bump). Adds support for all spoiled content through the TIE/A previews earlier this week (thanks to Geordan for letting me steal data from YASB), and adds support for obstacles.

Relevant obstacles commit here: https://github.com/elistevens/xws-spec/commit/ba7d7dd1bd8d115a093e35082548a916dd7bb2db

As per VS's request it's an optional squadron-level key that, if present, must contain 3 strings. No content enforcement is done beyond that. Once we finalize on what we're going to name them, we can tighten that down a bit and release v0.3.0 (or v1.0.0 or w/e).

Edit: side note, sorry for the lack of movement on my end of XWS lately. Life's been keeping me busy ever since store championships ended.

you can now search by region. http://lists.starwarsclubhouse.com/search_guide

search prefixes are country, state, city, and venue.

for example: 'p=Han AND (state=Illinois OR state=Wisconsin OR state=Indiana)' will return all the Han lists in Illinois, Wisconsin, or Indiana.

added a type filter.

type=Regional s=lambda

gets you all the space cows played at a Regional

Hi all,

I was out for a while so out of this discussion about obstacles too.

I think I will add them in my builder soon, as I added the objectives for STAR WARS ARAMADA.

Perhaps I will meet some difficulties on the way, I will see...

bye

I'd like to request a visual guide mapping each obstacle to their canonical name.

I'd like to request a visual guide mapping each obstacle to their canonical name.

I made a thread about officially naming obstacles HERE .

but here it is if you don't want the hyperlink.

I'd like to request a visual guide mapping each obstacle to their canonical name.

Hi geordan !

According to the previous posts, here is the pictures with the canonical names from wxs specs. It follow the obstacles order provided by FFG on the squad sheet.

bye

I'd like to add this image to the XWS spec as a reference, if that's all right.

Guys, can you run me real quick the squad importation procedure you'd use for a cryodex fueled tournament?

What do I tell my fellow players in terms of preparation prior to the event?

What can I quickly scan when they arrive to play the tournament?

I understood there was a push to do it via a QR code, is that finalized?

Is simply taking the voidstate squad # the current way to do things, while you add players to your tournament in cryodex?

My main goal is to save myself the 30-60 minute amount of work I have to do with the pile of printed squad papers after the event is done, where I manually recreate the squads under YASB and get a link for each player while I punch info into List Juggler.