A general way to define infinite
-
@redrum Yeah I was assuming either you keep supporting "-1" or you mass change such occurrences into the new way of defining infinite, for all repository maps. Now, the second solution would not be very nice on @RogerCooper.
Ok. So I understand that it is not possible to generally define an "infinite" symbol or practice, but each option and property would need specific update to add something that it reads as infinite.
Theorically, most actual cases the like are positives only, so they could use the "-1" solution, tho I really wonder if a better way is possible. Especially for properties, like battle rounds, that may be user editable, expecting the user to know that he has to input "-1" to mean unlimited doesn't feel right to me (I wouldn't image any games working like that).
-
@cernel said in A general way to define infinite:
Especially for properties, like battle rounds, that may be user editable, expecting the user to know that he has to input "-1" to mean unlimited doesn't feel right to me
How is expecting the user to know he has to input "infinite" or "+" any better?
-
@alkexr Main suggestion was no value equals infinite.
-
@cernel said in A general way to define infinite:
Main suggestion was no value equals infinite.
That changes nothing about the fact that the user has to know what denotes infinity.
-
@cernel Unless the information shows up on the user interface or you have something like a drop-down list or a numeric up-down which turns into "infinity" if you go below valid values.
"For the world is changing: I feel it in the water, I feel it in the earth, and I smell it in the air."
-
@alkexr That was mostly a side matter. The main matter here is being able to set infinite instead of writing 10000 or something. It may be there is not a user friendly way to do it, and this topic is open to suggestions.
-
@alkexr A drop down list would be a good addition also because now the user can't know (for numerical properties) what are the max and min unless by hitting them. Not sure if in this case the infinite symbol (∞) might be telling enough.
-
@alkexr
A while ago I wondered about adding a description to the <property> tag to help players understand these 'Map Options' better.See Map Options
Cheers...
-
@Cernel, @redrum, @alkexr
Just a thought on this topic. Most of the time that I use that big number is to reset a resource. So if resourceCount accepted '-reset-' as a value, then some of these negative large numbers would go away.I know that this does not help with things like 'Land Battle Rounds'.
Cheers...
-
@redrum In the meantime, if I guess it would be an easy touch, I suggest setting in the engine that every time a value or count equal to "10000" is read, the engine reads it as infinite, and documenting this in pact of steel. This would be a bit patchy, but can only make things a little more consistent, especially if documented. Probably, then, better not accepting values greater than "10000".
-
@cernel It would be exactly as patchy as just simply using 10000 as practically infinity, which is what we do now.
-
Various languages have double.positiveInfinity and double.negativeInfinity in some form.
But in terms of the battle calc, you could just have a checkbox for "fight to finish" then the actual background implementation doesn't show up in the UI. It's an extra click for calcing strafes though as "fight to finish" would be on by default.
-
@cernel I would suggest to add an
infinite=trueflag.eg:
<option name="attemptsPerTurn" infinite="true"/>
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login