Rishy

Members
  • Content Count

    36
  • Joined

  • Last visited

Community Reputation

44 Decent

1 Follower

About Rishy

  • Rank
    Villager

Recent Profile Visitors

801 profile views
  1. Foraging: Five-second ruler Edit: Botanizing: Spice girl/boy
  2. Clippers being an umbrella term for several sail plans, may in this way, also provide a basis for modular sail plans indeed. This way ships could be equipped with either square rig (full-rigged), fore-and-aft rig (schooner) or a combination of both (brigantine), to provide speed with respectively wind from the back, from the side and a compromise of both. Players could plan their optimal sail plan according to the current wind direction and speed. Replacing rigs should be a slightly more complicated procedure than equipping horseshoes for example though, possibly requiring the aforementioned dry docks. Edit: Combining square rigs and fore-and-aft rigs could also enable the option to hoist sails strategically, such as using all sails of a brigantine on your journey with wind in the back, while hoisting only the square rig on the journey back with wind in the front to decrease the speed penalty.
  3. For the Gods runes extracting runes sounds reasonable to me, as there are existing alternatives (dispel + new rune). For scavenger runes I fear that being able to extract and reuse these would become a new meta, where the point and RNG of Archaeology in itself would become obsolete.
  4. There's a faith swap without losing faith for priests in the loyalty store, could mayhaps (as a compromise) add one for followers as well, at a cost (in marks) where it would be roughly equal to the equivalent of 5 sleep powders, while negating the cooldown period. This way the costs/benefit would remain roughly equivalent if you cannot prepare by getting to 30 faith first, though still benefit from the free characteristics gains.
  5. Traitor Champignon Sea Serpent showed up today. Took a while to find it. Here it is with a sailboat for scale, props to Doctorchese for taking this image. Here it is chasing me to shore. Having a knarr for breakfast. Also, its last breakfast: Colossus for scale (and a tiny anthuman for scale at the colossus's foot): Sea serpent strangling the colossus, also a full side-view of the deed:
  6. Currently a newbie can row a boat as fast as a Veteran the Vibrant Light [Olympian Atlas] the Fourth. Higher body strength should allow one to, even according to Wogicâ„¢, propel themselves faster while rowing. This may lead to players choosing rowing boats in low winds over their Sizable Ship of Superfluous Sails.
  7. Incorrect item, delete pretty please
  8. From my experience this is due to queuing multiple actions before all previous actions have finished. Example with 20 mind logic (max. 3 queue): Que 3 actions; Finish two actions (one left in queue); Que 3 actions (queue overflows; following the 'you are too busy' prompt); Finish the third action (no rarity); Finish the fourth action (first on second queue) with potential rarity; Finish last two actions without rarity. Whilst it may seem that the seemingly 'second' action after creating the second queue turned rare, it is actually the first action of the second sequence, as the action prior was already (still) running. Like what is described below: And about this: RNG. Spent ten four years without a single affinity (of which 18 10 months prem) after which I got four in two weeks (two months ago). EDIT: forgot about the 'recent' change in affinity gains four years ago.
  9. So, along the lines of: Let's say that after completing 'Paved with Stone' journal, the player gets to choose one specilization, as by that time they should be slightly familiar with most skills. These would consist of e.g. Constructor (masonry + paving + carpentry etc. missions), Labourer (mining + digging + woodcutting), Chef (farming + fishing + cooking etc. missions), Ranger (animal taming/husbandry + gardening + forestry + foranizing missions) and variations hereof where missions should not be exclusive necessarily per specilization. With rewards varying from unique titles to affinity/timer bonuses. This way one would not be forced to follow the general journal, forcing one to become a jack of all trades, but could choose something that would be a better fit towards their roleplaying and enjoyment aspect.
  10. Finished rainbowifying part of the deed.
  11. That's actually a Brig, not a Caravel. Nevertheless I am heavily in favour of introducing new, bigger ships, which would go hand in hand with this option op loading and towing ships.
  12. Au contraire, we need bigger ships, that cannot pass through cave canals. Like cutters, clippers, modular ships where sails can be adjusted to weather; basically anything that has more sails than a caravel.
  13. So on the one hand we do not want fragmentation, though do want new places to explore. On the other hand we want to start over, but at the same time bring over old equipment and an existing market. NFI is designed to be separated from SFI for a reason, where players have started anew for a reason, not expecting for a merge to happen ever. If you did expect that, that would only boil down to having been giving false promises to yourself and potentially you would have been wasting your time. No announcements have been made or hinted to so far, because there likely is nothing to announce about this. How would it have been different from introducing more SFI servers? Would everyone in favour of merging the servers now, have been in favour of having had introduced new SFI island at the time instead? (If not, because of reasons stated above, then why wouldn't you have isolated yourself from the market, if not temporarily?) Honestly I see no difference in merging the servers now and having introduced more SFI servers instead. Can we all please make up our collective minds?
  14. Thanks, I managed to get it working on MXlinux KDE today as well, using a clean wineprefix. Earlier I ran into issues where it would not work using dotnet45 (stated as being required in the first post) and I had to use a winetricks version outside the one delivered in aptitude, using the --self-update argument.