[Dev Thread] Enhanced Thief Fan Missions Archive (Last update: 2017/12/24) - by EnYB0La
Shadowdancer on 1/8/2017 at 12:28
FM Keeper Annals?
*Who is Keeper Annals?* :rolleyes:
fortuni on 1/8/2017 at 12:51
Quote Posted by Yandros
Complete Thief Mission Archive?
If your going to include TDM missions it's arguable that having the word Thief in the title could be a little mis-leading unless you also included TDM.
ie Complete Thief & TDM Mission Archive?
How about 'Garrett's Grotto'?
As for the interface of TFKH, to my eyes there is too much whiteness in the interface, page after page of whiteness could be annoying, even difficult to read after to much scrolling up and down, some pastel colour would be a lot more accommodating.
TannisRoot on 1/8/2017 at 13:10
What's the name of that 'law' that any time a community project is announced everyone will spend 90% of the time arguing about what to call it? Lol
I have to say, "Garret's Grotto" sounds like a nsfw site :p
gamophyte on 1/8/2017 at 15:42
Quote Posted by Yandros
Complete Thief Mission Archive?
You got it. This is a place where all the missions are at yes? So it's like a library or archive. So keeper's library, or keeper mission library or what not makes more sense to me. Other synonyms for archive, or storage or the like. Keeper's Chambers? Keeper's Port?
EnYB0La on 7/12/2017 at 16:41
2017/12/07After months of mockups, studies and local researches, I decided to totally drop Angular and Bootstrap in order to be able to build easily my web application. I finally decided to use (
https://gohugo.io/) Hugo, which is a static website generator written in Go, which renders HTML views in milliseconds, which uses JSON/YAML data and which is really more simple to use compared to Angular.
Also and as discussed in this thread, I changed the name of the project from
The Former Keeper's House to something more generic and more understandable:
Enhanced Thief Fan Missions Archive.
I created a proper GitHub account and two repositories: (
https://www.github.com/etfma/)
The idea is that everyone can contribute to the database adding/updating Fan Missions Markdown files using Git/GitHub features. It is possible to add new fan missions to the database basing the YAML content architecture on this default archetype: (
https://raw.githubusercontent.com/etfma/etfma-website/source/archetypes/default.md)
The new content has to be pushed with a Pull Request in this repository: (
https://github.com/etfma/etfma-fanmissions)
I published a
README.md file to explain the steps to scaffold locally the application if someone wants to contribute: (
https://github.com/etfma/etfma-website)
Changelog1. Totally dropped Angular and Bootstrap in order to be able to build and use something more simple.
2. Scaffolded new project based on (
https://www.gohugo.io/) Hugo.
3. Created a proper Sass Framework for the project instead of using big Bootstrap.
4. Added Font Awesome as iconic visual framework.
5. Reworked JSON/YAML Fan Missions database.
6. Totally reworked web design for something more attractive/minimalist.
7. Changed project's name from
The Former Keeper's House to
Enhanced Thief Fan Missions Archive.
TechnologyHugo 0.30+
PreviewThis is a local test that shows retrieved Fan Mission YAML keys value into the main fanmission layout. I'm now working on creating a designed view based on this content.
The Header and the Footer are definitive.
(
https://image.ibb.co/jHTT5G/Screen_Shot_2017_12_07_at_13_30_41.png)
Inline Image:
https://preview.ibb.co/fJHczb/Screen_Shot_2017_12_07_at_13_30_41.pngEnYB0La on 7/12/2017 at 16:45
I'd like to know if the community can review this content archetype and tell me if a fan mission needs less or more information (maybe reviews?) [(
https://raw.githubusercontent.com/etfma/etfma-website/source/archetypes/default.md) source]:
Code:
title: ""
author:
name: ""
ttlgpropfileid: ""
details:
description: ""
game: ""
ttlgthread:
threadtitle: ""
url: ""
category: ""
contest:
name: ""
url: ""
languages:
- ""
version: ""
newdark:
isrequired: false
minrequiredversion: ""
originalreleasedate: ""
lastupdatedate: ""
characteristics:
hascustommotions: false
hascustomcreatures: false
hascustomobjects: false
hascustomsounds: false
hascustomtextures: false
hascustomscripts: false
hascustomgamesys: false
hasbgmusic: false
hasmovies: false
hasmap: false
hasautomap: false
hasbooksandscrolls: false
hasgoaldescription: false
extras:
download:
main:
sourcename: ""
url: ""
mirrors:
- sourcename: ""
url: ""
screenshots:
sourcename: ""
urls:
- ""
youtube:
videoid: ""
author:
name: ""
channelid: ""
walkthroughs:
- sourcename: ""
url: ""
language: ""
(
https://raw.githubusercontent.com/etfma/etfma-fanmissions/master/tma/death-s-cold-embrace.md) Here a real example.
It's really easy to understand. This is YAML, an alternative to JSON.
gamophyte on 7/12/2017 at 18:30
These are great. I can't get too deep into all that should be there but it may be important to consider incompatibility notations; Such when the author says a certain mod will mess up the intended experience of their mission either by hard errors, unintended changes to gameplay, or an insult to the aesthetics purveyed by the author. While some may argue they will get this info if they read readme, I would argue that not all authors may know until later and may not update a zip just to make new readme, and, it's just nice to see that right away in a filtered list.
EnYB0La on 8/12/2017 at 14:09
Quote Posted by gamophyte
[...] to consider
incompatibility notations; Such when the author says a certain mod will mess up the intended experience of their mission either by hard errors, unintended changes to gameplay, or an insult to the aesthetics purveyed by the author. [...]
Code:
details:
technicalinformation:
- ""
So, inspired by Yandros Death's Cold Embrace fan mission + this content archetype, the Markdown fille should be something like:
Code:
details:
technicalinformation:
- "Disable any upgrades or enhancement packs, including the EP or EP2. This isn't only because we want you to experience the missions the way they were designed; there were also numerous crashes during testing with EPs enabled."
- "Before beginning, check your Audio settings and make sure Audio Channels is set to at least 12. One tester had very bad issues with certain missions with it set below 12."
Should I consider to add two new entries:
author's gameplay tips and
FM credits?
gamophyte on 8/12/2017 at 15:05
Quote Posted by EnYB0La
Code:
Should I consider to add two new entries:
author's gameplay tips and
FM credits?
It seems like those are okay to be deeper, so if someone wanted to look into it they can, but I worry about making a sorted list too busy. But again I haven't fully considered how this will be visually.
