{"id":249,"date":"2011-06-14T03:37:00","date_gmt":"2011-06-14T09:37:00","guid":{"rendered":"http:\/\/elysianshadows.com\/2011\/06\/terrainselection-and-a-slight-comeback-from-marcel\/"},"modified":"2011-06-14T03:37:00","modified_gmt":"2011-06-14T09:37:00","slug":"terrainselection-and-a-slight-comeback-from-marcel","status":"publish","type":"post","link":"http:\/\/elysianshadows.com\/updates\/terrainselection-and-a-slight-comeback-from-marcel\/","title":{"rendered":"TerrainSelection and a Slight Comeback from Marcel"},"content":{"rendered":"\n

Presenting…<\/p>\n

[color=#0000BF][size=20]TOOLKIT: ALPHA[\/size][\/color]<\/p>\n

That’s right. Sitting in the repositories right now is the Alpha version of the Toolkit.<\/p>\n

[u]Alpha? As opposed to Beta, Gamma, or Delta?[\/u]<\/p>\n

Yup. I’ve realized the error in my ways–it does the team no good to have a Toolkit in development parallel to the engine if it’s not ALWAYS available. The reason I’m dubbing this version “Alpha” is that, whereas it is stable, it’s not fully [i]functional[\/i]. There’s an entire list of missing features, things that are blatantly broken, as well as placeholders.<\/p>\n

I am currently putting all my effort to get the Toolkit in both a “Stable’ AND “Functional” state. When it reaches this area, I will then entitle it the “internal Beta.” You guys crash test the internal, and finally we’ll end with the open (public) beta.<\/p>\n

[u]Uhh…if that much is wrong with it, then what the fuck? Why should I even bother trying it?[\/u]<\/p>\n

Because there’s a whole host of features that ARE implemented you need to see. In addition, any suggestions you give me now will make their way into the next stage of the build, the “internal beta.”<\/p>\n

[u]Features, eh? Elaborate.[\/u]<\/p>\n

[color=#0000FF]Selection System[\/color]<\/p>\n

Well, now that I’ve got your interest, lets take a look.<\/p>\n

<\/p>\n

To begin, notice the “red outline.” This is what I currently have selected. Yeah, that’s right–it’s most definately NOT a “square” as you see in most tile editors! By holding the “ctrl” button on windows and “apple’ button on mac while selecting tiles, you can continue your selection. This results in the ability to ‘stagger’ your selection. Here’s another good example:<\/p>\n

<\/p>\n

You can do this on the selection pane as well as on the world editor. <\/p>\n

[color=#0000FF]Improved UI[\/color]<\/p>\n

note the bottom panels. In order to conserve space, you no longer have the Tile and Object sheets in your face. Instead, the right panel displays the current sheet, and the left has the layer\/selection options. When you change the “edit” radio button to a layer that uses Tiles, the sheet on the right pane auto adjusts (and vice versa.) <\/p>\n

The “view” radio buttons enables\/disables the respective layer of tiles.<\/p>\n

[color=#0000FF]GTFO Hotkey[\/color]<\/p>\n

Hit “space” anytime while editing and the panel containing your tiles\/view options will go away. HURRAH FOR SPACE EFFICIENCY!D =D<\/p>\n

[color=#0000FF]de-fuckified menus[\/color]<\/p>\n

Mkay, so Falco actually did these…But I sure does like ’em better. suggestions\/ideas? Toy around w\/ em. I’ll get a better list going of the broken ones as well as the additional drop-downs I will be adding.<\/p>\n

<\/p>\n

[color=#0000FF]Reload Sheets[\/color]<\/p>\n

I think it’s worthwhile to mention that the “reload sheets” button on the left panel actually works–open up the current tilesheet in Paint, change shit, save, tap the button, and PRESTO.<\/p>\n

edit: I do recall pritam saying something about it not working with PS due to “multiple access errors.” I’ve never had a problem, but if anybody else here can replicate the issue and tell me what they did, I’d be happy to investigate deeper.<\/p>\n

[u]SWEET! So why’s this bitch an Alpha?[\/u]<\/p>\n

Yeaaaa…..about that. <\/p>\n

[color=#0000FF]Broken UI items[\/color]<\/p>\n

<\/p>\n

The items in the top left (^ and v arrows) as well as the top right (Terrain and Layer dropdowns) do nothing. Deprecated code still exists, and needs to be butchered. These are replaced by the new UI on the bottom left panel. <\/p>\n

View->Debug Selection does nothing.<\/p>\n

[color=#0000FF]Broken Debug System[\/color]<\/p>\n

Debug->View Log gives you a nice “THIS IS UNDER CONSTRUCTION!” message from Falco, then continues to pop an (empty) debug box:<\/p>\n

<\/p>\n

[color=#0000FF]Fucked Directory View[\/color]<\/p>\n

This is the most unfortunate part, and the most urgent. This is the NUMBER ONE priority. This bar is supposed to allow you to change between Projects, Levels and Areas, as well as change your “currently selected” for each of the aforementioned. Example: you’ve got a “level” selected, then goto Level->Add Area. This will add a new area to the current “level.” However, since you cannot change the current level view the directory view, you CAN NOT change your selection. In addition, I realize the UI is fucked:<\/p>\n

<\/p>\n

Obviously, that cannot be right. ;pp Blame Falco, and I’m on it.<\/p>\n","protected":false},"excerpt":{"rendered":"

Originally posted by Arce (Marcel Girgis) in our Private Development forum on 6.14.11.<\/strong><\/p>\n

So, as you already know, I’d taken some serious time off the ES project in order to fail.<\/p>\n

The last 6-8 months of my life were characterized by utter confusion. Drugs, time wasting, stupidity; all the things any self respecting human would strive to avoid. The worst part is the way I pretended like I was still an active ES member. Outch. ES has always been a source of pride an accomplishment for me…but I’d reached a state where I would genuinely try devving, only to be held back by my own lack of focus and impaired cognitive abilities. What had become the reason I awaited weekends, the activity I could feel good about regardless of my place in life, I have neglected.<\/p>\n

I’m not here to apologize. I don’t owe anybody here an apology (except myself).<\/p>\n

What I owe you is a Toolkit. That, and the assurance that I am now in the proper state of mind to be working again. Neither of these two things can be given in text; a “omg sorry!” post isn’t going to make up for the time I’ve been dead weight to the team. With this being said, allow me to begin with the long awaited update! <\/p>\n","protected":false},"author":1,"featured_media":243,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[],"class_list":["post-249","post","type-post","status-publish","format-standard","hentry","category-underlying-technology"],"_links":{"self":[{"href":"http:\/\/elysianshadows.com\/updates\/wp-json\/wp\/v2\/posts\/249","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/elysianshadows.com\/updates\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/elysianshadows.com\/updates\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/elysianshadows.com\/updates\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/elysianshadows.com\/updates\/wp-json\/wp\/v2\/comments?post=249"}],"version-history":[{"count":0,"href":"http:\/\/elysianshadows.com\/updates\/wp-json\/wp\/v2\/posts\/249\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/elysianshadows.com\/updates\/wp-json\/wp\/v2\/media\/243"}],"wp:attachment":[{"href":"http:\/\/elysianshadows.com\/updates\/wp-json\/wp\/v2\/media?parent=249"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/elysianshadows.com\/updates\/wp-json\/wp\/v2\/categories?post=249"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/elysianshadows.com\/updates\/wp-json\/wp\/v2\/tags?post=249"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}