User talk:SolSys/Etude

From Hearts of Iron 4 Wiki
Jump to navigation Jump to search

Techcell[edit]

Just had the idea – one more option – to use the {{techcell}} template at least for icon, name and effect. (Perhaps a disadvantage is that the template uses level 4 headings for the names.)

Focus Prerequisites Description
Army Effort icon

Army Effort

  • Army experience +5 Army experience
  • Atomic Research.png 50% Research bonus ( use):
Despite the increasing possibilities of aerial and naval warfare, ground combat is still key in tomorrow's wars. With preparation, we can avoid reliving the hell of the trenches.
Equipment Effort icon

Equipment Effort

  • Atomic Research.png 50% Research bonus ( use):
  • Infantry Weapons or Support Artillery
Goal generic allies build infantry.png Army Effort The limits for what equipment can be carried by infantry are constantly being pushed. We will focus on giving our troops the best tools available.
Equipment Effort II icon

Equipment Effort II

  • Atomic Research.png 50% Research bonus ( use):
  • Infantry Weapons or Support Artillery
Goal generic small arms.png Equipment Effort We will continue our efforts to ensure our infantry and support troops are armed with the best possible equipment of our time.

– Lillebror (talk) 18:55, 31 December 2016 (CET)

TBH, I just about thought on simply putting everything in {{effectbox}} under an image-map and let it be. The only reason to have it in a table is for the various sorting options [including effects - which the above doesn't have]. On another note, there doesn't seem to be too big a difference between {{techcell}} and {{effectbox}}. Maybe a merged template with more optional parameters [including border] might be better in the long run. ~ SolSys (talk) 19:43, 1 January 2017 (CET)
Just effectboxes have the disadvantage that they do not display the prerequisites and their bypasses. (They have also a very limited space if you don't make them wider.)
Sorting - I think that's not necessary.
I made the techcell template to fill the various boxes of the doctrine {{tree}}s. I thought that this is more flexible than integrate the content in the boxes (technically techcell is a subtemplate). … … …
Currently I prefer this version of a table:
Focus Prerequisites Effects Description
Goal generic construct infrastructure.png Metropolitan France None
The following will bypass the focus:
France does not own a state with at least 3 free building slots for Infrastructureinfrastructure in the strategic regions Northern or Southern France.
3 random states owned and controlled by France of the regions Northern or Southern France with at least 3 free infrastructure building slots get 3 Infrastructureinfrastructure levels. La Métropole should always come first. We can start by improving our infrastructure to create jobs and enable faster troop deployment.
– Lillebror (talk) 10:46, 2 January 2017 (CET)
Haven't really played the game so not sure about bypass - didn't check the files for anything other than what was needed for events [you can simply skip that focus?]. I have the old mockup page of what I had in mind for individual NF pages. It's not too far off from what you have. The premise is rather simple: a short intro, a big image-map tree [the old mockup is mask-based], tables in the sub-sections with back-to-image link. I'm aware that big images don't go well with small form factors, but so do big tables. ~ SolSys (talk) 12:07, 2 January 2017 (CET)


Note: the table is based on the Stellaris tech table.

Back to NF tree image.
Focus Effects Prerequisites Description
Goal generic construct infrastructure.png Metropolitan France
  • Infrastructure.png +3 Infrastructure in 3 random states if states:
    • Owned and controlled by Flag of France France
    • Have Infrastructure.png 3 empty infrastructure building slots
    • In the regions Northern France or Southern France
Bypass:
France does not own a state with at least 3 free building slots for Infrastructureinfrastructure in the strategic regions Northern or Southern France.
La Métropole should always come first. We can start by improving our infrastructure to create jobs and enable faster troop deployment.
Goal generic allies build infantry.png Army Effort
  • Army experience +5 Army experience
  • Atomic Research.png 50% Research bonus (1x uses):
    • Land Doctrine
Despite the increasing possibilities of aerial and naval warfare, ground combat is still key in tomorrow's wars. With preparation, we can avoid reliving the hell of the trenches.
Goal generic small arms.png Equipment Effort
  • Atomic Research.png 50% Research bonus (1x uses):
    • Infantry Weapons
    • Support Artillery
Goal generic allies build infantry.png Army Effort
Bypass:
France does not own a state with at least 3 free building slots for Infrastructureinfrastructure in the strategic regions Northern or Southern France.
The limits for what equipment can be carried by infantry are constantly being pushed. We will focus on giving our troops the best tools available.

~ SolSys (talk) 12:09, 2 January 2017 (CET)

Back[edit]

Do we need a 'back' button that links back to the image? (Or something similar?)– Lillebror (talk) 18:42, 10 January 2017 (CET)

That's a good question whose answer entirely depends on the design approach taken. It's needed on the mockup NF page since it is based on two main sections: the NF image tree and the NF descriptions.
I'd say it is not needed on the French NF page since you're using smaller images on the sub-sections. I would still recommend to swap the places of the Effects and Prerequisites columns.
While not exactly asked, I do prefer the use of a single big image for 3 main reasons:
  1. Easier navigation - makes reading and clicking on focuses easier.
  2. Visual information - seeing the "big picture" and getting part of the information at a glance [maybe even removing the need of mentioning them in the tables].
  3. Management - eliminating the need for keeping many images of the NF sub-sections. It's safe to assume the number of trees will grow so its supposed to reduce work required for file updating.
~ SolSys (talk) 09:51, 11 January 2017 (CET)