questions

Is the reason you have a 5,000,000 money cap because of the data type your storing in?

just making an inquiry, but im sure you could use an extended data type for the mney dimension of the game.

It was set deliberately like that in Bots2

But it shouldn´t stay at 5 mil imo. Raise it or remove completly.

Same, i dont know why it was capped in the first place.

i dont think it can be totally removed but up to about 37,000,000,000,000
im pretty sure its only capped because of the data type that is used im not sure about php or javascripts data types but long long is a data type in visual basic and c# using it for the money variable stored in the database could increase the money cap to 9,223,372,036,854,775,807 long long also increases the amount of space needed to store the data but a simple case statement could fix that problem.

I don´t know either. Perhaps from stopping peolpe having 5808204828492482849028209 kudos?

Well...didn´t see you there Gess...

Money cap should stay in place. No need for more than 5m

The 5,000,000 kudos limit is unrelated to technical limitations. That's how it was in bots2, so that's how it is in bots4. I don't really see a convincing reason to increase the cap at this point. If anything, I think it would just make it easier overall to get kudos as there would be more kudos floating around in the game.

If you're curious, MySQL offers signed and unsigned versions of 8, 16, 24, 32, and 64-bit integers. Kudos are currently stored as 24-bit unsigned integers, giving them a maximum possible value of 2^24 = 16,777,215 without changing the database schema.

I dont think the question is 'why should it be removed?'. A cap should have a clear reason. I cant think of any reason why the amount of money needs to be capped. And a cap without reason is pointless.

It even caused silly problems in Bots2; redis points were 5 million each for higher levels. But when you trained or fought, the repair costs were deducted from your capped total of 5 million, meaning you had to do a fight without any repairs, in order to buy a redis point.

or buy an item & sell it to make up the money ...

I like the cap. Flooding the market with excess kudos just makes everything all too easy.

The cap also applied to 1 day ordering. No matter how much the weapon/armour cost it was restricted to 5mil.

I'd still want there to be a cap because kudos aren't a scarce commodity. High level training bots get millions with every train, so it would be kind of silly to have a bot with billions of kudos. I could also see these fast earners creating inflation issues too. I could imagine reaching a point where it eventually makes no sense to train for kudos because there are so many more kudos already on bots to be taken via fighting. There needs to be some sort of sink in the kudos economy beyond what the showroom/equipment damage combination offers.

As for thinking about it as "why have a cap?", I tend to look at every proposed divergence from bots2 as "why should it be different?". I'm not against changing things from how they were (battles actually end at 0 hp now, crazy!), but I like to have a good reason for doing so.

Fine, communism it is. Mr Lunchbox will be thrilled :)

why shouldn't you change everything in bots4. you change the name you change the game. if all your looking to do is clone bots 2 then why start from scratch just get a hold of FLOR and hit him up for his original source code.

but if you plan on making a sequel then change and alter the game make it your own and take some pride in what your doing you're not FLOR you're ENDER. else wise just name it B2REMAKE and dont change a thing!!!

I've never claimed bots4 to be anything but a remake.

The initial release will be the same as bots2 and that new features will be added over time. I'm not against changing some things earlier, but there have to be convincing reasons for doing so.

As for copy/pasting floR's bots2 code (if that were even possible), programming is something I enjoy and so the process of creating the game is what makes it fun for me. I know the codebase better this way and it will be easier to extend later on.