Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalid number for finalNPCLevelMultiplier - Defualt value error #68

Open
duxck opened this issue Feb 21, 2019 · 3 comments
Open

Invalid number for finalNPCLevelMultiplier - Defualt value error #68

duxck opened this issue Feb 21, 2019 · 3 comments

Comments

@duxck
Copy link

duxck commented Feb 21, 2019

Get error with default values unchanged

image

When I try and change the IslandInstanceCustomDatas1 without changing any of the number values I get the following error.

If I change it from 1.0 to 1 it will trigger on InstanceTreasureQualityMultiplier instead.
So there seems to be an issue with default value with one decimal.

Works if I remove the decimal and save with the following values:
-1, 1 ,0 , 1, 0 - Gives error with -1, 1.0, 0, 1.0, 0.0

@noblackthunder
Copy link

noblackthunder commented Aug 5, 2019

image
Same issue here .. does not work on my pc at all windows 10 .. but on my Windows 2012r2 server where i can not zoom it works just fine

all i have to do is just to open it and click save .. no changes required to trigger that issue for me

@noblackthunder
Copy link

noblackthunder commented Aug 5, 2019

ok looking into this .. this seems like an odd .net bug that is easy to fix by developers and maybe even not to hard for normal users

everything that has to be done is make the expression bigger and give it a few more values actually (see what i marked in red )
image

basically NumberStyles.Float, CultureInfo.InvariantCulture, needs to be added and the reference
using System.Globalization;

and it should work just fine for floats ... it seems this is just a bug affecting floats for some reason in this solution .. might be a known bug in the targeted .net version fixed in other targeted versions

Edit... Also i hate windows forms .... WPF would have been so much better :P

@PejSwap
Copy link

PejSwap commented May 13, 2021

Hello I dig up the post ... I have the same concerns but despite the modifications of the code someone continues to do it to help?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants