[solved]

[IonS]

Closed!
[SOLVED]
​

 

[IonS]

bump ;x

 

[IonS]

bump, somebody?

 

[IonS]

bump..

 

[nclx]

1- Why would you want to change it?
2- Change the variable type ;s, i bet is uint32_t.

 

[IonS]

1- Why would you want to change it?
2- Change the variable type ;s, i bet is uint32_t.

but in which file? what's the variabels that I must to change?
I've tryied it, but i don't know if I've changed all teh variables needed..

 

[nclx]

I guess items.cpp and maybe items.h? im not checking it, im lazy, sry.

4294967295 (max value of uint32_t, isnt that enough?) ;s, i think that it is maybe even bigger than long unsigned int

edit:

ah no, long unsigned int is

18446744073709551615
xD

 

[Cykotitan]

[0.3.5pl1]

item.cpp, line 1212

[B][COLOR="Red"]u[/COLOR][/B]int32_t duration = item->getDuration() / 1000;

item.h, Line 149-151

		void setDuration([B][COLOR="Red"]u[/COLOR][/B]int32_t time) {setIntAttr(ATTR_ITEM_DURATION, time);}
		void decreaseDuration([B][COLOR="Red"]u[/COLOR][/B]int32_t time) {increaseIntAttr(ATTR_ITEM_DURATION, -time);}
		[B][COLOR="Red"]u[/COLOR][/B]int32_t getDuration() const {return getIntAttr(ATTR_ITEM_DURATION);}

items.cpp, line 890:

it.decayTime = std::max(([B][COLOR="Red"]u[/COLOR][/B]int32_t)0, intValue);

edit:

ah no, long unsigned int is

18446744073709551615
xD

That's uint64_t :S

 

[nclx]

basically is the same... i tested long unsigned int in ubuntu 9.10 64 bits... ;s

 

[Cykotitan]

aa but he use 32-bit os i think ;s

 

[nclx]

thats why is better to use variable data types from stdint.h, to make it standar, so is better to use the type that you gave, still dont know why would he change it ;s

 

[Cykotitan]

he want to make items that take a year to decay to another item or something

 

[IonS]

:///

 

[nclx]

if he want item to take a year to decay he can script it =(, no more posting here for me ;s

 

[IonS]

EDIT

it's not for a year ¬¬

 

[IonS]

Bump

 

[Rexxar]

Well, going by your logic, items can have a duration of 24.8 days.

Do you really wish to have items with THAT long of a duration?

If that's the case then wouldn't be better to just add a separate column in the player_items table, where you input the UNIX-TIME when the item was added to the player, and then have an onlogin script or something that checks if the item has "expired" and thus removes it if that's the case.

 

[IonS]

Well, going by your logic, items can have a duration of 24.8 days.

Do you really wish to have items with THAT long of a duration?

If that's the case then wouldn't be better to just add a separate column in the player_items table, where you input the UNIX-TIME when the item was added to the player, and then have an onlogin script or something that checks if the item has "expired" and thus removes it if that's the case.

good idea, but i want it to other purpose, must be by source editing :/

 

[IonS]

bump

 

[IonS]

bump