Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
more
Author Message
x77x
Master
**

Posts: 488
Likes Given: 0
Likes Received: 15 in 15 posts
Joined: Mar 2012
Reputation: -4



Post: #1
more
.set more 2d on a guildstone gets you 02
.set more1 2d on a guildstone gets you 02

if you do it with a script you can get 2d, but not manually, it converts it to dec

im noticing this all over the place, shits get converted back and forth

Dragons of Time 2000-2020
http://dragonsoftime.com
05-28-2017 12:35 PM
Find all posts by this user Like Post Quote this message in a reply
pointhz
Journeyman
*

Posts: 148
Likes Given: 1
Likes Received: 55 in 28 posts
Joined: Oct 2013
Reputation: 1



Post: #2
RE: more
probably because it doesnt support text but only hex
05-29-2017 12:17 AM
Find all posts by this user Like Post Quote this message in a reply
Coruja
Sphere Developer
*****

Posts: 987
Likes Given: 5
Likes Received: 226 in 187 posts
Joined: Jul 2012
Reputation: 7

Dimension Shard

Post: #3
RE: more
MORE / MORE1 are set and read as hex values, so you must store it correctly as hex number using prefix 0, like 02d instead 2d

probably it's returning the wrong value to you because storing it as 2d will make sphere try to convert this to hex, and since "2d" is not a valid hex value, it will just convert the "2" ignoring the "d", so 2 (dec) = 02 (hex)

PS: MORE and MORE1 are the same thing and both are stored as MORE1. The only difference is that MORE always return the raw value (hex number) and MORE1 can format the result depending on the item typedef (eg: MORE1 on t_spawn_char will return the char defname "c_something" instead an hex number). When the item typedef don't have any formatting available it will also return the hex raw value by default
05-29-2017 01:31 PM
Find all posts by this user Like Post Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)