Talk:Paving
Jump to navigation
Jump to search
- Is there is a way to place wikitables more compact? or i just need to rework this page and create a brand new table? current list is too long..
- --Kitsuneg (talk) 13:32, 20 May 2018 (EDT)
looks like the ' style="display: inline-table;" ' will allow tables to exist next to each other.
--Ricky (talk) 23:16, 20 May 2018 (EDT)
- >style="display: inline-table;"
- Aha ... I had not spotted that one yet.
- In addition, in this particular case (theoretical/not tested), ditching the 'result' column and putting the 'name' and 'image' vertically in the same row (with or without using row-span) could be an option to get all tables displayed next to each other (depends on used display-screen resolution on the viewers side of course. ie: might work for you/some/most, but not for all).
- +(adjusting/playing-around a bit with the floating game-images is probably also needed to get all tables next to each other in this case.)
- --.MvGulik. 12:30, 22 May 2018 (EDT)
- If needed or desired one could fix/lock those tables next to each other by putting them into a additional surrounding container table. like here.
- Although that probably will not play well on portable device displays.
- --.MvGulik. 03:10, 23 May 2018 (EDT)
Pavement Order
- Additional data dump.
- (overlayed BY > X > overlays ON)
- --.MvGulik. 03:56, 6 January 2020 (EST)
Data: (in-game observation)
- xxx: (... > (xxx) > ...)
Data: (map/grid file data)
- Stones updated. Insufficient data on others. (... one option not tried yet)
- (thinking about a potential hafen-cache scanner(python3), to be used by others, to select map-grid-files with additional useful pavement-order data)
- --.MvGulik. 11:02, 11 January 2020 (EST)
- (thinking about a potential hafen-cache scanner(python3), to be used by others, to select map-grid-files with additional useful pavement-order data)
- Map/Grid file-data issue:
- (never mind custom client stuff, it makes no real sense after some more thinking. Probably game/map-server hiccup related.) In some cache map-grid files(3) a single pavement-type was using a none default position. This position change was not consistent to pavement-type, or: in one file pavement-A was mis-ordered, while in an other file pavement-B was mis-ordered while pavement-A was not mis-ordered. - (effect not seen in-game) --.MvGulik. 14:20, 11 January 2020 (EST)
(ore: res vs rob) argentite, Silvershine ilmenite, Heavy Earth limonite, Iron Ochre hematite, Bloodstone sylvanite, Schrifterz plessite, Meteorite petzite, Direvein nagyagite, Leaf Ore magnetite, Black Ore
Newer pavement Images
Erm. The new game-res source images are 512x512 JPG's, and there also still significant smaller than 128x128 downsized PNG's.(looked at the wrong JPG file, PNG is ~50% of source) Still thinking about switching from PNG to JPG (and than also for similar cases). And in that case it might not be a bad idea to also group them in there own folder(s).
Will take some time to ponder about this some more. So in the mean time ... feel free to add some additional points of view on this. --.MvGulik. 17:38, 10 December 2020 (UTC)