Jump to content

  •  

Bug Tracker Migration

June 3rd
Good news everyone! The staff has decided that it is time to slowly kill off this Bug Tracker. We will begin the process of slowly migrating from this Bug Tracker over to our Github Issues which can be found here: https://github.com/HerculesWS/Hercules/issues

Over the next couple of days, I will be closing off any opportunity to create new reports. However, I still will keep the opportunity to reply to existing Bug Reports. Doing this will allow us to slowly fix any bug reports we have listed here so that we can easily migrate over to our Issue Tracker.

Update - June 7th 2015: Creating new bug posts has been disabled. Please use our https://github.com/HerculesWS/Hercules/issues tracker to post bugs. Users are still able to reply to existing bug posts.

- Administration

Issue Information

  • #008715

  • 0 - None Assigned

  • Needs More Info

Issue Confirmations

  • Yes (1)No (1)
Photo

Official Cash Points

Posted by kyeme on 02 June 2015 - 01:16 PM

On Hercules, the variable of Cash Points is #CASHPOINTS I think that the Cash Points of official server is stored in 'login-server' and it should be ##CASHPOINTS.

Because in official, the Rok Points (pRO Cash Points) can be use on the whole server of Character(s) that alone the login-server.
Please confirm thank you.

##vars are buggy, char server doesn't retain them last I checked (it will discard them if login server is offline).

Disclaimer: I have not checked in some time.

changed status to: Working as Intended

Strongly against using a ##variable regardless of Aegis behaviors, since login servers are often shared between production and test servers.

It's the same reason why our bank implementation isn't at the login server level either.

Ohh okay. I dont know if the 'login-server' I said was correct. What I mean is that the CASHPOINTS should be stored in `login` tables.

Like this: `birthdate` `character_slots` `pincode` `pincode_change` `cashpoints`

Is this possible and safe? Thank you.

Not safe at all (the login table is handled by the login server, and shared between all character servers that use the same login server).

How about the account_data table (where the bank is stored)? That would be possible.

changed status to: Needs More Info

In aegis works differently, there is a DB to store the values of Cash.
CREATE TABLE [dbo].[Cash](
	[AID] [int] NOT NULL,
	[Cash] [int] NOT NULL,
PRIMARY KEY CLUSTERED