#Illivium Zero improvements

1 messages · Page 1 of 1 (latest)

frigid flicker
#

UI/Controls

  • Add an option to disable the auto-centering on buildings when you click on it. On a bigger screen that just leads to a lot of unnecessary scrolling
  • Clicking on the empty terrain should automatically close any opened window or menu at the bottom of the screen when you have a building selected, etc. Forcing a click on the "Close, X" is unintuitive and just another hindrance that can be avoided
    -Review the marketplace tabs. Having the accepted offers/collect mixed in with offers to be accepted is not a good design and makes scrolling through it cumbersome. The offers to be accepted should be in 1 tab, the offers already accepted/pending to be collected in another and the your own offers in a third tab

Orthograph

  • Carbon, Silicon, Hydrogen Converters
    :-> "converts other Elements in to Carbon" should be "into"

Misc.

  • Remove the popup when you level up. Just another useless click that becomes annoying. Maybe use a small animation on the level's label instead
  • When viewing the list of all your lands, the active land should be highlighted
  • An option to have a constant grid on the map. Maybe lighter than when you are building/moving structures?
mossy flower
#

Agree on the Level Up useless click, it's a hinderance when you just want to quickly go through and tidy things up when you have limited time.

primal garnet
#

Every time you claim you get 1 or 2 levels.... I would be content with like a yellow light circling the level in the top corner 💛

Screenshot_20230609_222218_Illuvium_Zero.jpg
mossy flower
cinder grove
#

moving the window to a screen with a different resolution makes some things unclickable.

#

Pumps and extractors shouldn't need to be told to mine (since they cost no ressources to do so and its extremely annoying since it adds a lot of useless clicks to land management )

#

option to hide or remove the F2p plot

alpine lily
#

ILVzero on mobile: collecting in marketplace moves the whole screen back to the top, I would rather have it stay put as is with accepting offers

muted meadow
#

Quality of Life Upgrade: Currently, you can only see upgrade costs when the building is not in use. Once you start an activity, the tab for upgrading vanishes, and you can't see what it would cost to take the building to the next level. This makes it difficult to plan resources when you have to wait 24 hours before you can check again.

However, listing the resources required for the next upgrade under 'info' would significantly help in planning and management of resources.

formal granite
#

Love all the ideas in here. I'd also like the ability to rotate the buildings. Plus be able to see what area a building takes up even if you cannot build it yet. I feel this would make layout and planning way less cumbersome.

jaunty chasm
cinder grove
#

Can't click on crypton rift located directly behind Hydrogen pump lvl 4.

muted meadow
next trail
#

Hey folks, the UI/UX will get a pretty big go over in the Open Beta, on some specific things posted here:

  • Auto center off sounds like a good option.
  • Click on empty will be in, I hate that X too.
  • Marketplace was only ever a rough placeholder it will be redone by a UX designer.
  • Level ups will have milestones which award stuff (e.g. unlock a structure or get an extra builder), only the "Milestone" level which give you something new like 10, 100, 500 will have pop-ups requiring a click. The others will just be a subtle effect.
  • @gilded pilot
lavish tangle
formal granite
next trail
#

Probably not for Open Beta.

mossy flower
#

For those of us testing would be awesome if we were offered a discount on a plot of land according to what level we have achieved. eg the higher the Level the higher the discount one is eligible for. Good incentive to keep playing the next few months. A lot of our spare time is going into testing this game as you know.

primal garnet
uneven wren
primal garnet
uneven wren
muted meadow
formal granite
cinder grove
#

Plants grow too much and provide too much gold coins imo. If we want people to use the shop to buy coins this would need to be drastically reduced, like 90% less.

#

The plants hinder efficiency so they can keep growing and this will make sure people log in everyday to weed whack, but their gold drops could be reduced.

formal granite
formal granite
primal garnet
formal granite
empty hound
#

I think this suggestion highlights an underlying need to make a JIRA board public and allow the community to vote on those feature requests. I've submitted 50+ issues/feature requests just for zero myself and have no visibility at all into if/where those are at in the roadmap.

Opening up the JIRA roadmap may be a scary proposition, but also the answer can't turn into the community generating IIPs for every little thing that seems to be taking too long to develop. This will pull the team away from other critical efforts that the community may not see and be an inefficient use of time long-term compared to providing this visibility up-front.

While I completely agree with the changes suggested here, I'm voting thumbs down because I do not think this is a good process for suggesting changes. Even if the whole community voted for items like these, how is the team supposed to prioritize them compared with all the others and everything else that must be developed?

uneven wren
empty hound
# uneven wren This is just feedback. It's not an iip.

Yes, not sure what you're saying here though. Are you saying it's more productive to put feedback here and have discussions on each piece of feedback rather than using the ticket system and allowing the team to use their expertise to evaluate these requests?

uneven wren
#

So it's not Like every Team member has to read throught this Chanel to gather all the feedback or ideas

empty hound
#

Not sure how that works, I do see Johnny commented though

uneven wren
#

Ofc everyone who Like can read and ad a comment... Community members and Team members.
But it's not an Obligation for both

empty hound
#

Point is, this is in no way scalable

#

You could have 100 feature requests that the whole community agrees with that equate to 5+ years of dev time.....now what?

uneven wren
#

Don't we have 4 payed guys to watch that Chanel?

#

Then it is @ council Stage and will get discussed what is good what is Bad and then good ones get to Team which give priorities i guess..
Idk, i'm no Team member i don't See the whole process Step by step

empty hound
#

I do not think the council should be managing and prioritizing feature requests, we need to let the game designers build the game

#

and allow the community to provide feedback in a way that isn't redundant (note Johnny says most of the requests on this one are already planned)

uneven wren
#

I guess you should write an iip to delete gaming and community council then 😂

empty hound
#

Their purpose is high-level direction, not micro management of new features

uneven wren
#

You sure?

empty hound
#

I sure hope so!

uneven wren
#

Maybe one of the council members can verify the whole process... How it is Set up?

empty hound
#

Just because this is web3 with a DAO and council doesn't mean it's completely different from normal product development, where you also have external stakeholders and customer advisory boards.

uneven wren
#

Sure

#

Afaik if an iip gets reaction(40 upvotes for now) it gets discussed in the subcouncil council, where also 1 of the Team is sitting in. From there it goes to the Main council for a Final vote. But i could be wrong

empty hound
#

Same for feedback like this?

uneven wren
#

No, just iips afaik

empty hound
#

So here the author needs to take the feedback and decide if they want to push it forward by making an IIP next?

uneven wren
empty hound
#

Way too much fuss for simple UI improvements...

small gull
empty hound
#

Specifically, opening up JIRA?

small gull
# empty hound Good to hear, has this been discussed already? https://discord.com/channels/7603...

While we have discussed the desire for the community to see ongoing lists of features like this ( so that the same items don't get requested over and over again) this specific idea has not yet been proposed. I'll make sure they're aware of this suggestion, though personally I am not sure this method would be feasible. Since certain items are under NDA internally as well as with other partners making a working JIRA board public would not be possible.

empty hound
prisma rock
# empty hound I think this suggestion highlights an underlying need to make a JIRA board publi...

Opening up a Jira is definitely not the way to go.

Feedback and suggestions are items that team takes note of but the latter has prerogative if they will implement them or not. Its definitely not a good idea for the DAO to affect development on a granular level.

Even if items go through a specific proposal and gets passed at this level (25+ upvotes), these items will be aligned with the team as to its feasibility. Sometimes the team themselves would post in the thread if they 1) confirm working on it already 2) cant do it at all or without adding scope creep/delays and etc.

And if it is something the team can do, at the end of the day, the team would need to determine the timeline of the deployment.

empty hound
prisma rock
empty hound
prisma rock
# empty hound So what do you think about sharing specific issues only?

I think an overall update would be great but not something i'd mandate unless it went through a proper IIP process.

ex.

Feedback submitted to via the game itself or here would not necessarily be tracked. But if Julien would give updates about it thats team prerogative.

But for items that passed as a proposal, I would like it to be constantly part of the updates Julien gives.

Back then we even had monthly dev blogs and it was a great way to monitor certain big ticket items for updates.

edited for grammar mistakes. my bad.

empty hound
# prisma rock I think an overall update would be great but not something i'd mandate unless it...

Big ticket items or major features are very easy to handle communication on, but how will you prevent hundreds of requests for the same little UI improvements like this thread is about? How many times should someone need to respond to these in discord? Who is really going to spend the time updating the community on these?

It needs to be scalable.

JIRA is a great tool for sharing a prioritized list of some of these smaller items along with the big ones. People who care can then check there before submitting a new ticket or raising issues in discord, even vote for the item they want to see implemented. I'm fine if this isn't the answer, but what are you proposing then?

prisma rock
small gull
#

My understanding is community members want to make sure that time isn’t wasted by suggested a UI or feature change that has the possibility of having been suggested and approved or rejected multiple times. Try to help save time from both a community and team standpoint.

empty hound
#

Yes, especially for minor improvements like this. We should not need a thread on these. They should not then need to go to an IIP. You can see above that Johnny says most of these were already planned to begin with. It's all wasted effort.

#

If you've been in zero chat you've seen these same requests dozens of times over the last two months as well. There are surely many support tickets on these same things too.

#

I want a place where I can look at a list of pending changes, ensure what I want to see is on that list, see where on that list it's prioritized, click on the ones I like to vote for (potentially causing them to move up in priority per my voting feedback to the team and per their decision), and create a new support ticket only for the ones that are not there already.

small gull
#

I think having an itemized list of incoming features is reasonable. One suggestion I heard recently that I liked was a reddit style forum inside the game launcher, searchable so people could check other posts, etc. Just a random idea from another community member but

The main issue I have with maintaining these kinds of lists is the amount of time it would take team members to maintain them, and that's where I get stuck when trying to come up with solutions.

Another problem to overcome is terminology. The team knows the specific names for items and aspects of the game but the community does not. The same thing could be described 20 different ways or searched 20 different ways for that matter. Someone could think their idea is original simply because they're using different words to describe the UI or feature.

Also simply having a list doesn't solve all the perceived problems. For example, if something was considered but rejected are we then going to maintain a rejection list as well.

Personally, I am all for finding a way that works the hard part is the solution 😅 though I certainly wouldn't want prioritization determined by the community. Being able to see the popularity of a suggestion is invaluable to see the pain points the community is dealing with, so again if we can gauge by up votes or down votes etc that's a lovely data point, but the community rarely has an idea of the scale to each of the solutions or implementations of features. What seems simple could take weeks, better to leave that to the professionals.

😝 just a crumb of what we've been discussing and considering when trying to find a way that would work for everyone. Seems like a simple request but comes with a ton of angles to be considered.

empty hound
# small gull I think having an itemized list of incoming features is reasonable. One suggesti...

Thanks for sharing what has been discussed. I completely agree with all you say here and think this is where using JIRA could be beneficial:
1 - Minimal maintenance because JIRA is already used for issues and those issues are already prioritized in a backlog. Team would only need to add a label to make it public and ensure it has a public friendly description (again, making some assumptions on what JIRA allows for public views)
2 - Rejected issues can still be kept as a record in JIRA, at the bottom of the list. Easy to add an indication of this (e.g. "[REJECTED}" in front of description), but if community wants to continue voting for it maybe there's a need to open the discussion back up again
3 - Community will never see everything on the full dev backlog in JIRA, and needs to accept the team's judgement on most prioritization, but I've found that showing a list from JIRA like this allows people to recognize there may be other more important items ahead of a specific issue, so they can better accept that it may not make it until next year instead of continuing to push and debate

small gull
small gull
prisma rock
empty hound
uneven wren
primal garnet
small gull
uneven wren
frail peak
uneven wren
frail peak
formal granite
formal granite